From: Badari Pulavarty <pbadari@us.ibm.com>
To: Jan Kara <jack@suse.cz>
Cc: linux-fsdevel@vger.kernel.org,
LKML <linux-kernel@vger.kernel.org>,
Andrew Morton <akpm@linux-foundation.org>
Subject: Re: Is nobh code still useful?
Date: Thu, 17 Sep 2009 21:21:37 -0700 [thread overview]
Message-ID: <4AB30AD1.7010400@us.ibm.com> (raw)
In-Reply-To: <20090917135627.GB13660@duck.suse.cz>
Jan Kara wrote:
> Hi,
>
> during my page_mkwrite() work, I've looked at who uses nobh_ versions of
> various functions in fs/buffer.c. It seems only ext2 and jfs use them. ext3
> uses them only from writepage() (which means we needn't attach buffers to a
> page when it was written via mmap in writeback mode) and ext4 tries to use
> them but in fact it's nop because it always attaches buffers to the page
> earlier. So it's not really widely used, there's quite some code to support
> it (including one page flag), and it also slightly complicates my
> page_mkwrite() fixes.
> So I wanted to ask does somebody actually remember what it is good for?
> Buffer heads obviously consume some memory so was that the reason? OTOH we
> have to map the page whenever we write to it or send it to disk via
> writepage().
>
>
Originally it was supported on ext2. I added support nobh support for
ext3. At that time, the main
issue/complaint was that, these bufferheads consume memory from
ZONE_NORMAL causing
memory pressure on 32-bit (i386) configurations.
Thanks,
Badari
next prev parent reply other threads:[~2009-09-18 4:21 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-09-17 13:56 Is nobh code still useful? Jan Kara
2009-09-17 15:11 ` Boaz Harrosh
2009-09-17 15:25 ` Jan Kara
2009-09-18 4:21 ` Badari Pulavarty [this message]
2009-09-18 14:12 ` Theodore Tso
2009-09-18 14:25 ` Arjan van de Ven
2009-09-20 18:17 ` Jan Kara
2009-09-23 14:16 ` Christoph Hellwig
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=4AB30AD1.7010400@us.ibm.com \
--to=pbadari@us.ibm.com \
--cc=akpm@linux-foundation.org \
--cc=jack@suse.cz \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@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 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.