From: anupam.kapoor@gmail.com (anupam kapoor)
To: kernelnewbies@lists.kernelnewbies.org
Subject: U64 Ordering in File System Code of Btrfs
Date: Thu, 28 Aug 2014 11:42:59 +0530 [thread overview]
Message-ID: <87bnr5p2fo.fsf@gmail.com> (raw)
In-Reply-To: <53FEB617.2020400@gmail.com> (nick's message of "Thu, 28 Aug 2014 00:54:47 -0400")
>>>>> [Thu, 28 Aug 2014 00:54:47 -0400]: "nick" (nick):
,----[ nick ]
| Hey Guys,
| Thanks for the help so far. I am wondering after reading the btrfs
| code for certain functions there seem to
| be a lot of u64 variable and function returns of this type. Is this
| common in file system due to the disk
| being in a certain format and depending on the CPU being big or small
| endian that this needed to not reorder
| the disk parts that are being read into main memory and preserve the data's ordering?
| Cheers Nick
`----
on disk format is little-endian.
have a look at https://btrfs.wiki.kernel.org/index.php/Main_Page for
more information.
kind regards
anupam
next prev parent reply other threads:[~2014-08-28 6:12 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-08-28 4:54 U64 Ordering in File System Code of Btrfs nick
2014-08-28 6:12 ` anupam kapoor [this message]
2014-08-28 18:11 ` nick
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=87bnr5p2fo.fsf@gmail.com \
--to=anupam.kapoor@gmail.com \
--cc=kernelnewbies@lists.kernelnewbies.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;
as well as URLs for NNTP newsgroup(s).