From: Mike Christie <mikenc@us.ibm.com>
To: device-mapper development <dm-devel@redhat.com>
Subject: Re: New -udm?
Date: Mon, 11 Apr 2005 15:56:57 -0700 [thread overview]
Message-ID: <425B00B9.7000804@us.ibm.com> (raw)
In-Reply-To: <C2EEB4E538D3DC48BF57F391F422779321A8EF@SRMANNING.eng.emc.com>
goggin, edward wrote:
>
> I don't see a way around needing to use pre-allocated bio memory
> which is reserved strictly for this purpose -- albeit it is possible
> that a single bio could be reserved for making progress in serial
> fashion across all multipaths which are in this state.
>
>
Hey back on the subject of bio allocations. Is failback going to stay
in userspace? If so, the bio allocation there suffers from the same
problem. Would it work to have a fs_bio_set and block_bio_set so
the allocations coming into the block layer would use the fs set and
everything below (like block/scsi_ioctl or hw handlers) would use the
block layer one (today everyone uses the fs_bio_set which causes problems)?
If you stacked multipath on top of multipath I guess this would not work.
Or will you need per device bio sets?
For sg io there other allocations, so this just handles the bio itself.
next prev parent reply other threads:[~2005-04-11 22:56 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-04-11 17:36 New -udm? 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 [this message]
-- strict thread matches above, loose matches on Subject: below --
2005-04-10 19:29 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
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
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=425B00B9.7000804@us.ibm.com \
--to=mikenc@us.ibm.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.