linux-fsdevel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Robert W. Fuller" <orangemagicbus@sbcglobal.net>
To: linux-fsdevel@vger.kernel.org
Subject: nobh option to ext2
Date: Sat, 01 Jan 2005 18:45:58 -0500	[thread overview]
Message-ID: <41D73636.4080405@sbcglobal.net> (raw)

I must first admit I'm a bit of a newbie.  That having been said, what 
exactly does the nobh option to ext2 do?  Perhaps you can recommend 
resources to me that detail the interaction between the memory manager 
and the file systems?  I'm looking for something that means more to me than:

"Implements a new set of block address_space_operations which will never
   attach buffer_heads to file pagecache.  These can be turned on for ext2
   with the `nobh' mount option.

   During write-intensive testing on a 7G machine, total buffer_head
   storage remained below 0.3 megabytes.  And those buffer_heads are
   against ZONE_NORMAL pagecache and will be reclaimed by ZONE_NORMAL
   memory pressure.

   This work is, of course, a special for the huge highmem machines.
   Possibly it obsoletes the buffer_heads_over_limit stuff (which doesn't
   work terribly well), but that code is simple, and will provide relief
   for other filesystems.


   It should be noted that the nobh_prepare_write() function and the
   PageMappedToDisk() infrastructure is what is needed to solve the
   problem of user data corruption when the filesystem which backs a
   sparse MAP_SHARED mapping runs out of space.  We can use this code in
   filemap_nopage() to ensure that all mapped pages have space allocated
   on-disk.  Deliver SIGBUS on ENOSPC."

Regards,

Rob

             reply	other threads:[~2005-01-01 23:46 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-01-01 23:45 Robert W. Fuller [this message]
2005-01-02  0:10 ` nobh option to ext2 Robert W. Fuller

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=41D73636.4080405@sbcglobal.net \
    --to=orangemagicbus@sbcglobal.net \
    --cc=linux-fsdevel@vger.kernel.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).