From: Werner Almesberger <wa@almesberger.net>
To: Jens Axboe <axboe@suse.de>
Cc: linux-fsdevel@vger.kernel.org
Subject: Re: elevator priorities vs. full request queues
Date: Tue, 22 Jun 2004 16:08:59 -0300 [thread overview]
Message-ID: <20040622160859.I1325@almesberger.net> (raw)
In-Reply-To: <20040622101434.GB12881@suse.de>; from axboe@suse.de on Tue, Jun 22, 2004 at 12:14:35PM +0200
Jens Axboe wrote:
> Don't think I posted any newer ones, I'll see if I can get something
> posted today/tomorrow (or at least before going on vacation thursday).
Seems that I picked a good moment for starting to ask around :-)
> And I'd like to pass in priority through the
> bio, like described further down.
Good, so that's the way to go then.
> It doesn't sound too complicated :)
You haven't seen the tiny little per-page trees hanging off
each requests yet ;-) I need them to "upgrade" requests when
someone with high priority decides to request a page that's
already in the queue. That should be a comparably rare event,
but handling that certainly adds complexity :-(
Thanks,
- Werner
--
_________________________________________________________________________
/ Werner Almesberger, Buenos Aires, Argentina wa@almesberger.net /
/_http://www.almesberger.net/____________________________________________/
next prev parent reply other threads:[~2004-06-22 19:09 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 [this message]
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
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=20040622160859.I1325@almesberger.net \
--to=wa@almesberger.net \
--cc=axboe@suse.de \
--cc=linux-fsdevel@vger.kernel.org \
/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.