From: Tokunori Ikegami <ikegami.t@gmail.com>
To: Caleb Sander <csander@purestorage.com>
Cc: linux-nvme@lists.infradead.org
Subject: Re: [PATCH] nvme: convert little endian NVME definitions to native format
Date: Tue, 17 Sep 2024 06:24:45 +0900 [thread overview]
Message-ID: <e75fdfbf-e503-40fe-9252-28e905bafb53@gmail.com> (raw)
In-Reply-To: <CADUfDZo=WwCTWwmY+UcUA7zpXb9CMpOsNC0icat7opwwFpJh=A@mail.gmail.com>
Okay I will do check the actual behavior again. (Since I thought the
definition value works as little endian byte order on the big endian
environment.) Thank you.
On 2024/09/17 3:12, Caleb Sander wrote:
> Why not? CPUs assume native byte order for all arithmetic operations.
> The fact that you could print this value implies it must be
> represented in native byte order. Non-native endianness is only
> relevant when interacting with byte-addressable data external to the
> CPU (storage, network, etc.).
next prev parent reply other threads:[~2024-09-16 21:24 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-09-16 15:42 [PATCH] nvme: convert little endian NVME definitions to native format Tokunori Ikegami
2024-09-16 16:12 ` Caleb Sander
2024-09-16 16:41 ` Tokunori Ikegami
2024-09-16 18:12 ` Caleb Sander
2024-09-16 21:24 ` Tokunori Ikegami [this message]
2024-09-17 14:31 ` Tokunori Ikegami
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=e75fdfbf-e503-40fe-9252-28e905bafb53@gmail.com \
--to=ikegami.t@gmail.com \
--cc=csander@purestorage.com \
--cc=linux-nvme@lists.infradead.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox