From: Andrew Morton <akpm@digeo.com>
To: Nick Piggin <piggin@cyberone.com.au>
Cc: kernel@kolivas.org, linux-kernel@vger.kernel.org
Subject: Re: [BENCHMARK] 2.5.70-mm2 with contest
Date: Mon, 2 Jun 2003 17:54:10 -0700 [thread overview]
Message-ID: <20030602175410.5f198657.akpm@digeo.com> (raw)
In-Reply-To: <3EDBEC27.9070705@cyberone.com.au>
Nick Piggin <piggin@cyberone.com.au> wrote:
>
> It will be interesting to see what happens if we set the
> ext3 journal write paths as PF_SYNCWRITE. I'll try some tests
> a bit later today.
>
OK.
Longer-term it would be best to lose the PF_SYNCWRITE thing and to just
mark the BIOs as synchronous prior to submitting them. It's a matter of
transferring the info in writeback_control.sync_mode at the pagecache/BIO
boundary: mpage_bio_submit(), __block_write_full_page->submit_bh(), etc.
But we can worry about that later, once it is established that the
synchronous write detection is sufficiently useful.
next prev parent reply other threads:[~2003-06-03 0:40 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-06-02 22:06 Con Kolivas
2003-06-02 22:16 ` Andrew Morton
2003-06-03 0:30 ` Nick Piggin
2003-06-03 0:54 ` Andrew Morton [this message]
2003-06-03 1:00 ` Nick Piggin
2003-06-03 0:44 ` Pasi Savolainen
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=20030602175410.5f198657.akpm@digeo.com \
--to=akpm@digeo.com \
--cc=kernel@kolivas.org \
--cc=linux-kernel@vger.kernel.org \
--cc=piggin@cyberone.com.au \
/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
all inboxes | Powered by JetHome®