All of lore.kernel.org
 help / color / mirror / Atom feed
From: xerofoify@gmail.com (nick)
To: kernelnewbies@lists.kernelnewbies.org
Subject: U64 Ordering in File System Code of Btrfs
Date: Thu, 28 Aug 2014 14:11:53 -0400	[thread overview]
Message-ID: <53FF70E9.8070704@gmail.com> (raw)
In-Reply-To: <87bnr5p2fo.fsf@gmail.com>



On 14-08-28 02:12 AM, anupam kapoor wrote:
>>>>>> [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
> 
Forget to check the wiki and found what I was looking for. In addition, the code docs for the kernel
are some of the best I am ever seen, the only three that even compare are the Yocto Project, Arch Wiki
and Red Hat docs. Now I understand why you guys state to read the docs first :).
Cheers Nick 

      reply	other threads:[~2014-08-28 18:11 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
2014-08-28 18:11   ` nick [this message]

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=53FF70E9.8070704@gmail.com \
    --to=xerofoify@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.