From: Joe Thornber <thornber@redhat.com>
To: Miquel van Smoorenburg <miquels@cistron.nl>
Cc: linux-lvm@sistina.com, thornber@redhat.com
Subject: [linux-lvm] Re: dm, dm_table, request_queue
Date: Mon Feb 23 15:36:01 2004 [thread overview]
Message-ID: <20040223203731.GA14731@reti> (raw)
In-Reply-To: <20040223163106.GA22231@cistron.nl>
On Mon, Feb 23, 2004 at 05:31:08PM +0100, Miquel van Smoorenburg wrote:
> And, in general, do you feel this is the correct solution ?
No, I'm going to do what Jens Axboe suggested and add a congestion
function into the request_queue itself. dm will therefore provide its
own congestion function that takes the targets into account. I think
this is the opposite of what you're suggesting, devices look downwards
to their children devices rather than up to their parents.
- Joe
next prev parent reply other threads:[~2004-02-23 20:37 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-02-23 11:30 [linux-lvm] dm, dm_table, request_queue Miquel van Smoorenburg
2004-02-23 15:36 ` Joe Thornber [this message]
2004-02-23 19:20 ` [linux-lvm] " Miquel van Smoorenburg
2004-02-24 4:02 ` Joe Thornber
2004-02-24 5:26 ` Miquel van Smoorenburg
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=20040223203731.GA14731@reti \
--to=thornber@redhat.com \
--cc=linux-lvm@redhat.com \
--cc=linux-lvm@sistina.com \
--cc=miquels@cistron.nl \
/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.