From: Hannes Reinecke <hare@suse.de>
To: device-mapper development <dm-devel@redhat.com>,
Mike Snitzer <snitzer@redhat.com>
Cc: linux-block@vger.kernel.org, lsf-pc@lists.linux-foundation.org
Subject: Re: [LSF/MM ATTEND] plan to deprecate old .request_fn request-based code path?
Date: Wed, 13 Jan 2016 09:21:24 +0100 [thread overview]
Message-ID: <56960904.5060006@suse.de> (raw)
In-Reply-To: <alpine.LRH.2.02.1601121835590.29321@file01.intranet.prod.int.rdu2.redhat.com>
On 01/13/2016 12:39 AM, Mikulas Patocka wrote:
>
>
> On Tue, 12 Jan 2016, Mike Snitzer wrote:
>
>> Hi,
>>
>> I'd like to attend LSF/MM and as the subject covers I'd like to at least
>> participate in a discussion about plans (realistic or not) for
>> removing/deprecating the old .request_fn path in block core and block
>> drivers.
>>
>> The request-based DM code (only used for multipath) has gotten more
>> complex to support both old .request_fn and blk-mq (and stacking
>> combinations: .request_fn ontop of blk-mq paths, blk-mq ontop of
>> .request_fn paths). Simplifying DM core in this area would be nice.
>>
>> One of the hurdles has been blk-mq doesn't yet have a scheduler. I know
>> Jens had/has something in the works. But there is also the question of
>> whether DM's top-level blk-mq request_queue should be trained to
>> leverage/stack underlying blk-mq request_queue capabilities (Keith Busch
>> was going to look at this aspect in the context of multipath on NVMe but
>> I never heard anything from Keith on that). As of now DM multipath's
>> blk-mq request_queue only supports a single (virtual) hw queue.
>>
>> In addition to the above topic, I'd be open to discussing Linux MD
>> maintainership options with others if for some reason that is still an
>> unresolved situation come mid April.
>>
>> Thanks,
>> Mike
>
> Convert multipath from request-based to bio-based and these problems in
> device mapper core will disappear :-)
>
We have been down that road already. It doesn't work.
There is a reason why we switched to request-based multipathing.
Cheers,
Hannes
--
Dr. Hannes Reinecke Teamlead Storage & Networking
hare@suse.de +49 911 74053 688
SUSE LINUX GmbH, Maxfeldstr. 5, 90409 Nürnberg
GF: F. Imendörffer, J. Smithard, J. Guild, D. Upmanyu, G. Norton
HRB 21284 (AG Nürnberg)
next prev parent reply other threads:[~2016-01-13 8:21 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-01-12 18:59 [LSF/MM ATTEND] plan to deprecate old .request_fn request-based code path? Mike Snitzer
2016-01-12 23:39 ` Mikulas Patocka
2016-01-13 8:21 ` Hannes Reinecke [this message]
2016-01-13 11:02 ` Alasdair G Kergon
2016-01-15 15:28 ` Benjamin Marzinski
2016-01-15 16:19 ` Mike Snitzer
2016-01-13 11:16 ` Sagi Grimberg
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=56960904.5060006@suse.de \
--to=hare@suse.de \
--cc=dm-devel@redhat.com \
--cc=linux-block@vger.kernel.org \
--cc=lsf-pc@lists.linux-foundation.org \
--cc=snitzer@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox