linux-fsdevel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Nick Piggin <npiggin@gmail.com>
To: Christoph Hellwig <hch@infradead.org>
Cc: Nick Piggin <npiggin@kernel.dk>, linux-fsdevel@vger.kernel.org
Subject: Re: [patch 3/4] fs: introduce inode dirty state helpers
Date: Tue, 23 Nov 2010 00:44:25 +1100	[thread overview]
Message-ID: <AANLkTik8J-tL2ass4D48k1gN4jkRx=RybZszsOL5Qjbg@mail.gmail.com> (raw)
In-Reply-To: <20101122132552.GC25321@infradead.org>

On Tue, Nov 23, 2010 at 12:25 AM, Christoph Hellwig <hch@infradead.org> wrote:
> On Tue, Nov 23, 2010 at 12:07:33AM +1100, Nick Piggin wrote:
>> Inode dirty state cannot be securely tested without participating properly
>> in the inode writeback protocol. Some filesystems need to check this state,
>> so break out the code into helpers and make them available.
>>
>> This could also be used to reduce strange interactions between background
>> writeback and fsync. Currently if we fsync a single page in a file, the
>> entire file gets requeued to the back of the background IO list, even if
>> it is due for writeout and has a large number of pages. That's left for
>> a later time.
>
> If you want filesystems to use the helpers they need to be exported,
> and good kerneldoc comments so that filesystem writers know what they
> need to do.

You're right, of course. I sent a half-baked patch there sorry. (Well, it should
be working quite well, but it needs exports and decent kerneldoc as you say).

Will send an update tomorrow.

  reply	other threads:[~2010-11-22 13:44 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-11-22 13:05 [patch 1/4] fs: mark_inode_dirty barrier fix Nick Piggin
2010-11-22 13:06 ` [patch 2/4] fs: fsync inode dirty race fix Nick Piggin
2010-11-22 13:23   ` Christoph Hellwig
2010-11-22 13:43     ` Nick Piggin
2010-11-22 13:07 ` [patch 3/4] fs: introduce inode dirty state helpers Nick Piggin
2010-11-22 13:25   ` Christoph Hellwig
2010-11-22 13:44     ` Nick Piggin [this message]
2010-11-22 13:09 ` [patch 4/4] ext2: inode sync fixes Nick Piggin
2010-11-22 13:16 ` [patch 1/4] fs: mark_inode_dirty barrier fix 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='AANLkTik8J-tL2ass4D48k1gN4jkRx=RybZszsOL5Qjbg@mail.gmail.com' \
    --to=npiggin@gmail.com \
    --cc=hch@infradead.org \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=npiggin@kernel.dk \
    /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).