From: Joe Thornber <thornber@redhat.com>
To: Miquel van Smoorenburg <miquels@cistron.nl>
Cc: Joe Thornber <thornber@redhat.com>, linux-lvm@sistina.com
Subject: [linux-lvm] Re: dm, dm_table, request_queue
Date: Tue Feb 24 04:02:06 2004 [thread overview]
Message-ID: <20040224090356.GD14731@reti> (raw)
In-Reply-To: <20040224002116.GA6965@drinkel.cistron.nl>
On Tue, Feb 24, 2004 at 01:21:16AM +0100, Miquel van Smoorenburg wrote:
> All in all, I think that the first approach is the simplest and
> therefor the best.
>
> So how does this look:
Better wrt keeping mapped_device out of dm-table.c. But it still has
the problem that it treats congestion in any subdevices equally (which
may be a good approximation to start with).
I'll stick this in my pending queue, and look at it later in the week.
I think you're quite close, given that Jens doesn't want the
backing_dev pointer in the queue.
Thanks,
- Joe
next prev parent reply other threads:[~2004-02-24 9:03 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 ` [linux-lvm] " Joe Thornber
2004-02-23 19:20 ` Miquel van Smoorenburg
2004-02-24 4:02 ` Joe Thornber [this message]
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=20040224090356.GD14731@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.