From: Lars Marowsky-Bree <lmb@suse.de>
To: device-mapper development <dm-devel@redhat.com>
Cc: Alasdair G Kergon <agk@redhat.com>
Subject: Re: New -udm?
Date: Mon, 11 Apr 2005 10:46:11 +0200 [thread overview]
Message-ID: <20050411084611.GA12752@marowsky-bree.de> (raw)
In-Reply-To: <20050411011444.GA3748@osdl.org>
On 2005-04-10T18:14:44, Dave Olien <dmo@osdl.org> wrote:
> You're correct. I'll rewrite it on Thursday this week.
> I'll use the same methods Lars used in the dm-emc.c
Note that dm-emc.c also would need to pre-allocate it's requests, but
doesn't right now :/
Pre-allocating the requests sucks: Either we pre-allocate for _every_
path we might potentially need to send the request down on, or fix up
the request for the path we sent it down on (which would require us to
use internal knowledge about the req structs we're not supposed to
have).
Good solutions solicited ;-)
Sincerely,
Lars Marowsky-Brée <lmb@suse.de>
--
High Availability & Clustering
SUSE Labs, Research and Development
SUSE LINUX Products GmbH - A Novell Business
next prev parent reply other threads:[~2005-04-11 8:46 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-04-10 19:29 New -udm? Lars Marowsky-Bree
2005-04-10 20:25 ` christophe varoqui
2005-04-10 23:36 ` Dave Olien
2005-04-10 23:36 ` Mike Christie
2005-04-11 1:14 ` Dave Olien
2005-04-11 8:46 ` Lars Marowsky-Bree [this message]
2005-04-11 9:27 ` Mike Christie
2005-04-11 9:34 ` Mike Christie
2005-04-11 9:56 ` Mike Christie
2005-04-11 11:43 ` Lars Marowsky-Bree
2005-04-11 11:53 ` Mike Christie
-- strict thread matches above, loose matches on Subject: below --
2005-04-11 17:36 goggin, edward
2005-04-11 18:25 ` Mike Christie
2005-04-11 18:26 ` Mike Christie
2005-04-11 18:31 ` Mike Christie
2005-04-11 22:56 ` Mike Christie
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=20050411084611.GA12752@marowsky-bree.de \
--to=lmb@suse.de \
--cc=agk@redhat.com \
--cc=dm-devel@redhat.com \
/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.