From: Jens Axboe <axboe@suse.de>
To: Werner Almesberger <wa@almesberger.net>
Cc: linux-fsdevel@vger.kernel.org
Subject: Re: elevator priorities vs. full request queues
Date: Tue, 13 Jul 2004 14:35:44 +0200 [thread overview]
Message-ID: <20040713123541.GA28956@suse.de> (raw)
In-Reply-To: <20040713092904.A1795@almesberger.net>
On Tue, Jul 13 2004, Werner Almesberger wrote:
> > Maybe it would be more logical to assign 'default' priority in
> > bio_init(), in fact?
>
> What made me shy away from this is that bio_init and bio_alloc
> seem to get called from contexts where "current" wouldn't
> necessarily have anything to do with the process that has
> actually initiated the IO.
>
> For example, I'm not sure if the calls from ide-scsi.c, when
> it builds requests piece by piece, are safe in this regard.
That's not really what I meant - 'default' priority isn't tied to the
process. It's just that if default io prio was something other than 0,
then it would make sense to set it there. Say if the range was 0-15, and
you wanted 7 to be 'in the middle' default priority.
But I suppose you just want io submission to set it, in which case it
doesn't matter what bio_init() sets it to.
--
Jens Axboe
next prev parent reply other threads:[~2004-07-13 12:35 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-06-22 4:25 elevator priorities vs. full request queues Werner Almesberger
2004-06-22 7:48 ` Jens Axboe
2004-06-22 8:26 ` Werner Almesberger
2004-06-22 10:14 ` Jens Axboe
2004-06-22 19:08 ` Werner Almesberger
2004-06-23 10:14 ` Jens Axboe
2004-06-23 12:46 ` Werner Almesberger
2004-06-23 16:46 ` Jens Axboe
2004-06-23 16:57 ` Werner Almesberger
2004-06-23 17:00 ` Jens Axboe
2004-06-23 23:02 ` Werner Almesberger
2004-07-12 23:52 ` Werner Almesberger
2004-07-13 5:37 ` Jens Axboe
2004-07-13 12:29 ` Werner Almesberger
2004-07-13 12:35 ` Jens Axboe [this message]
2004-07-13 16:36 ` Werner Almesberger
2004-07-13 16:59 ` Jens Axboe
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=20040713123541.GA28956@suse.de \
--to=axboe@suse.de \
--cc=linux-fsdevel@vger.kernel.org \
--cc=wa@almesberger.net \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.