From: Christoph Hellwig <hch@infradead.org>
To: Michael Clark <michael@metaparadigm.com>
Cc: Alexander Viro <viro@math.psu.edu>,
Mark Peloquin <markpeloquin@hotmail.com>,
linux-kernel@vger.kernel.org, torvalds@transmeta.com,
evms-devel@lists.sourceforge.net
Subject: Re: [Evms-devel] Re: Linux v2.5.42
Date: Mon, 14 Oct 2002 16:21:34 +0100 [thread overview]
Message-ID: <20021014162134.C17683@infradead.org> (raw)
In-Reply-To: <3DA9B05F.8000600@metaparadigm.com>; from michael@metaparadigm.com on Mon, Oct 14, 2002 at 01:41:51AM +0800
On Mon, Oct 14, 2002 at 01:41:51AM +0800, Michael Clark wrote:
> From the discussion so far:
>
> Pros
> * Simplify ioctl routing to plugins
* allow code reuse
* simplify userspace access to intermediate layer
* avoid data duplication
* avoid having different data structures for very differen things
> Cons
> * Chew up a minor
> * Get a block device we don't need or want (ie. we can still easily
> directly access the underlying physical block devices)
> * loose purely logical remapping abstraction in plugins
Explain the exact meaning of this to non/native speakers like me, please
> * Complicate mapping of request queues to devices (ie. shouldn't only
> the top level volume device and the underlying physical devices need
> request queues)
You need struct request queue as data structure, but you don't actually
need a queue. Please check the code.
And no, I don't think having a peoper, custom make_request_fn will
complicate the code.
next prev parent reply other threads:[~2002-10-14 15:15 UTC|newest]
Thread overview: 53+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-10-12 17:14 Linux v2.5.42 Mark Peloquin
2002-10-12 19:34 ` Alan Cox
2002-10-12 19:37 ` jbradford
2002-10-13 23:55 ` Rob Landley
2002-10-13 12:41 ` [Evms-devel] " Michael Clark
2002-10-13 13:49 ` Christoph Hellwig
2002-10-13 15:16 ` Michael Clark
2002-10-13 15:35 ` Christoph Hellwig
2002-10-13 16:11 ` Brian Jackson
2002-10-13 16:26 ` Arjan van de Ven
2002-10-13 17:06 ` Brian Jackson
2002-10-13 19:58 ` Mark Hahn
2002-10-13 19:57 ` Rik van Riel
2002-10-13 20:26 ` Sean Neakums
2002-10-24 11:45 ` Alexander Kellett
2002-10-13 19:59 ` Andrew Morton
2002-10-13 20:24 ` Bernd Eckenfels
2002-10-14 15:11 ` Christoph Hellwig
2002-10-14 22:27 ` Bernd Eckenfels
2002-10-14 4:55 ` [Evms-devel] " Andreas Dilger
2002-10-13 17:46 ` Robert Love
2002-10-13 18:34 ` Brian Jackson
2002-10-14 4:23 ` [Evms-devel] " Andreas Dilger
2002-10-14 16:08 ` Christoph Hellwig
2002-10-14 14:45 ` Christoph Hellwig
2002-10-13 16:18 ` [Evms-devel] " Michael Clark
2002-10-13 17:10 ` Alexander Viro
2002-10-13 17:41 ` Michael Clark
2002-10-14 4:43 ` Andreas Dilger
2002-10-14 16:16 ` Christoph Hellwig
2002-10-14 15:21 ` Christoph Hellwig [this message]
2002-10-14 14:42 ` Shawn
2002-10-14 15:15 ` Christoph Hellwig
2002-10-14 14:20 ` Shawn
2002-10-14 16:15 ` Rik van Riel
2002-10-14 21:34 ` Shawn
2002-10-14 16:21 ` Christoph Hellwig
2002-10-14 16:38 ` Jeff Garzik
2002-10-14 21:47 ` Shawn
2002-10-15 7:42 ` Heinz J . Mauelshagen
2002-10-14 21:48 ` Oliver Neukum
2002-10-14 21:55 ` Shawn
2002-10-14 22:35 ` Oliver Neukum
2002-10-14 22:53 ` Shawn
2002-10-14 23:04 ` Oliver Neukum
2002-10-14 23:16 ` Alexander Viro
2002-10-14 23:30 ` Oliver Neukum
2002-10-15 0:10 ` Andrew Clausen
2002-10-14 22:57 ` Alexander Viro
2002-10-13 13:41 ` Christoph Hellwig
-- strict thread matches above, loose matches on Subject: below --
2002-10-14 23:57 [Evms-devel] " Mark Peloquin
2002-10-15 14:51 Steve Pratt
2002-10-15 21:18 ` Andrew Clausen
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=20021014162134.C17683@infradead.org \
--to=hch@infradead.org \
--cc=evms-devel@lists.sourceforge.net \
--cc=linux-kernel@vger.kernel.org \
--cc=markpeloquin@hotmail.com \
--cc=michael@metaparadigm.com \
--cc=torvalds@transmeta.com \
--cc=viro@math.psu.edu \
/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.