From: Aaron Straus <aaron@merfinllc.com>
To: Nick Piggin <npiggin@suse.de>
Cc: Adrian Hunter <adrian.hunter@nokia.com>,
"chris.mason@oracle.com" <chris.mason@oracle.com>,
"david@fromorbit.com" <david@fromorbit.com>,
Andrew Morton <akpm@linux-foundation.org>,
"Bityutskiy Artem (Nokia-D/Helsinki)"
<Artem.Bityutskiy@nokia.com>, LKML <linux-kernel@vger.kernel.org>
Subject: Re: [RFC][PATCH] mm: write_cache_pages be more sequential
Date: Mon, 7 Sep 2009 11:12:53 -0700 [thread overview]
Message-ID: <20090907181253.GA29904@merfinllc.com> (raw)
In-Reply-To: <20090907144514.GC28054@wotan.suse.de>
[-- Attachment #1: Type: text/plain, Size: 756 bytes --]
On Sep 07 04:45 PM, Nick Piggin wrote:
> > I meant that only part of the page was written. e.g.
> > write 10240 bytes, wait for writeback, then write another
> > 10240 bytes. The pages will be written out in the order
> > 0, 1, 2, 3, 4, 2
>
> OK...
>
> I guess it is a reasonable workaround for the problem. It is a bit
> unsatisfying to special case on a page basis like this, but anyway
> I don't think there should be a realistic downside in practice.
*NOTE* we also see this in NFS (I think) where a file is written to
sequentially yet readers will see holes in the file.
This is allowed behavior for NFS but annoying. So a work-around would
be great!
=a=
--
===================
Aaron Straus
aaron@merfinllc.com
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 191 bytes --]
next prev parent reply other threads:[~2009-09-07 18:35 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-09-07 14:07 Adrian Hunter
2009-09-07 14:15 ` Nick Piggin
2009-09-07 14:29 ` Adrian Hunter
2009-09-07 14:45 ` Nick Piggin
2009-09-07 18:12 ` Aaron Straus [this message]
2009-09-09 8:03 ` Adrian Hunter
2009-09-14 15:44 ` Artem Bityutskiy
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=20090907181253.GA29904@merfinllc.com \
--to=aaron@merfinllc.com \
--cc=Artem.Bityutskiy@nokia.com \
--cc=adrian.hunter@nokia.com \
--cc=akpm@linux-foundation.org \
--cc=chris.mason@oracle.com \
--cc=david@fromorbit.com \
--cc=linux-kernel@vger.kernel.org \
--cc=npiggin@suse.de \
/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
Powered by JetHome