From: "Michael Rubin" <mrubin@google.com>
To: Fengguang Wu <wfg@mail.ustc.edu.cn>
Cc: a.p.zijlstra@chello.nl, akpm@linux-foundation.org,
linux-kernel@vger.kernel.org, linux-mm@kvack.org,
Chris Mason <chris.mason@oracle.com>
Subject: Re: [patch 1/1] Writeback fix for concurrent large and small file writes
Date: Tue, 4 Dec 2007 01:06:06 -0800 [thread overview]
Message-ID: <532480950712040106r144ed43m5cb77cc394e2ec8a@mail.gmail.com> (raw)
In-Reply-To: <396386387.18082@ustc.edu.cn>
On Nov 29, 2007 5:32 PM, Fengguang Wu <wfg@mail.ustc.edu.cnwrote:
> > On Nov 28, 2007 4:34 PM, Fengguang Wu <wfg@mail.ustc.edu.cn> wrote:
> > > Could you demonstrate the situation? Or if I guess it right, could it
> > > be fixed by the following patch?
Feng I am sorry to have been mistaken but I reran my tests and I am
now finding that the patch you gave me is NOT fixing the problem. The
patch I refer to is the one you posted on this thread that adds a
requeue_io in __sync_single_inode.
I tarred up my test code. It is still in very rough shape but it can
reproduce the issue. You can find it here:
http://neverthere.org/mhr/wb/wb-test.tar.bz2
Just make the test and run it with the args "-duration 0:5:0
-starvation". You must be root so it can set some sysctl values.
> One major concern could be whether a continuous writer dirting pages
> at the 'right' pace will generate a steady flow of write I/Os which are
> _tiny_hence_inefficient_.
>
> So it's not a problem in *theory* :-)
>
> > I will post this change for 2.6.24 and list Feng as author. If that's
> > ok with Feng.
I am going to try to track down what is up in 2.6.24 and see if I can
find a less dramatic fix than my tree patch for the short term. If you
get a chance to reproduce the problem with my test on your patch that
would rock.
I still would like to see my full patch accepted into 2.6.25. A patch
should be arriving shortly that will incorporate my larger patch and
Qi Yong's fix for skip-writing-data-pages-when-inode-is-under-i_sync.
http://www.gossamer-threads.com/lists/linux/kernel/849493
As always thanks for your patience,
mrubin
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org. For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>
next prev parent reply other threads:[~2007-12-04 9:06 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-11-28 19:29 [patch 1/1] Writeback fix for concurrent large and small file writes Michael Rubin
[not found] ` <E1IxXMP-0002i8-4S@localhost>
2007-11-29 0:34 ` Fengguang Wu
2007-11-29 19:51 ` Michael Rubin
2007-11-29 20:16 ` Michael Rubin
[not found] ` <E1IxukV-0003Ns-5C@localhost>
2007-11-30 1:32 ` Fengguang Wu
2007-12-04 9:06 ` Michael Rubin [this message]
2007-11-29 2:13 ` Frans Pop
2007-11-29 6:58 ` Michael Rubin
-- strict thread matches above, loose matches on Subject: below --
2007-12-11 2:02 Michael Rubin, Michael Rubin
2007-12-12 20:55 ` Peter Zijlstra
2007-12-12 23:03 ` Michael Rubin
[not found] ` <E1J89kR-0001v3-CJ@localhost>
2007-12-28 7:35 ` Fengguang Wu
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=532480950712040106r144ed43m5cb77cc394e2ec8a@mail.gmail.com \
--to=mrubin@google.com \
--cc=a.p.zijlstra@chello.nl \
--cc=akpm@linux-foundation.org \
--cc=chris.mason@oracle.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=wfg@mail.ustc.edu.cn \
/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).