From: Andrew Morton <akpm@osdl.org>
To: Jens Axboe <axboe@suse.de>
Cc: neilb@suse.de, nathans@sgi.com, linux-kernel@vger.kernel.org,
drepper@redhat.com, mtk-manpages@gmx.net,
nickpiggin@yahoo.com.au
Subject: Re: [patch 1/1] sys_sync_file_range()
Date: Mon, 3 Apr 2006 14:21:30 -0700 [thread overview]
Message-ID: <20060403142130.1868c0e3.akpm@osdl.org> (raw)
In-Reply-To: <20060403143100.GH4647@suse.de>
Jens Axboe <axboe@suse.de> wrote:
>
> > > I don't think any disagrees with you, the sync-write process flag is
> > > indeed an atrocious beast...
> >
> > Yeah. PF_SYNCWRITE was a performance tweak for the anticipatory scheduler.
> > As cfq is using it as well now (hopefully to good effect) I guess it could
> > be formalised more.
>
> Yup, both 'as' and 'cfq' would prefer to just look at a SYNC bio flag
> instead. But the logic itself is definitely needed.
hm. I actually thought we were already doing that. We should at least
tranfer PF_SYNCWRITE into bi_flags at the point where we start to construct
the BIO.
That might well fix RAID, too. If it's handing work off to another thread
via BIOs.
next prev parent reply other threads:[~2006-04-03 21:19 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-03-30 7:41 akpm
2006-03-30 7:58 ` Neil Brown
2006-03-30 8:11 ` Andrew Morton
2006-03-30 8:32 ` Andrew Morton
2006-03-30 8:55 ` Neil Brown
2006-03-30 15:31 ` OGAWA Hirofumi
2006-03-30 20:19 ` Andrew Morton
2006-03-30 21:17 ` Nathan Scott
2006-04-03 1:24 ` Neil Brown
2006-04-03 7:50 ` Jens Axboe
2006-04-03 8:27 ` Andrew Morton
2006-04-03 14:31 ` Jens Axboe
2006-04-03 21:21 ` Andrew Morton [this message]
2006-04-04 20:50 ` Luck, Tony
2006-04-04 21:00 ` Andrew Morton
2006-04-04 21:01 ` Randy.Dunlap
2006-04-04 21:03 ` Ulrich Drepper
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=20060403142130.1868c0e3.akpm@osdl.org \
--to=akpm@osdl.org \
--cc=axboe@suse.de \
--cc=drepper@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mtk-manpages@gmx.net \
--cc=nathans@sgi.com \
--cc=neilb@suse.de \
--cc=nickpiggin@yahoo.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®