All of lore.kernel.org
 help / color / mirror / Atom feed
From: Hannes Reinecke <hare@suse.de>
To: "Nicholas A. Bellinger" <nab@linux-iscsi.org>
Cc: Greg KH <greg@kroah.com>,
	ksummit-2013-discuss@lists.linuxfoundation.org,
	Jens Axboe <axboe@kernel.dk>,
	James Smart <James.Smart@Emulex.Com>,
	linux-scsi <linux-scsi@vger.kernel.org>,
	LKML <linux-kernel@vger.kernel.org>,
	James Bottomley <jbottomley@parallels.com>,
	Andrew Vasquez <andrew.vasquez@qlogic.com>,
	kmo@daterainc.com, target-devel <target-devel@vger.kernel.org>,
	Tejun Heo <tj@kernel.org>, Christoph Hellwig <hch@lst.de>,
	scameron@beardog.cce.hp.com
Subject: Re: [Ksummit-2013-discuss] [ATTEND] scsi-mq prototype discussion
Date: Fri, 12 Jul 2013 12:52:37 +0200	[thread overview]
Message-ID: <51DFDFF5.80702@suse.de> (raw)
In-Reply-To: <1373592815.7397.477.camel@haakon3.risingtidesystems.com>

On 07/12/2013 03:33 AM, Nicholas A. Bellinger wrote:
> On Thu, 2013-07-11 at 18:02 -0700, Greg KH wrote:
>> On Thu, Jul 11, 2013 at 05:23:32PM -0700, Nicholas A. Bellinger wrote:
>>> Drilling down the work items ahead of a real mainline push is high on
>>> priority list for discussion.
>>>
>>> The parties to be included in such a discussion are:
>>>
>>>   - Jens Axboe (blk-mq author)
>>>   - James Bottomley (scsi maintainer)
>>>   - Christoph Hellwig (scsi)
>>>   - Martin Petersen (scsi)
>>>   - Tejun Heo (block + libata)
>>>   - Hannes Reinecke (scsi error recovery)
>>>   - Kent Overstreet (block, per-cpu ida)
>>>   - Stephen Cameron (scsi-over-pcie driver)
>>>   - Andrew Vasquez (qla2xxx LLD)
>>>   - James Smart (lpfc LLD)
>>
>> Isn't this something that should have been discussed at the storage
>> mini-summit a few months ago?
> 
> The scsi-mq prototype, along with blk-mq (in it's current form) did not
> exist a few short months ago.  ;)
> 
>>  It seems very specific to one subsystem to be a kernel summit topic,
>> don't you think?
> 
> It's no more subsystem specific than half of the other proposals so far,
> and given it's reach across multiple subsystems (block, scsi, target),
> and the amount of off-list interest on the topic, I think it would make
> a good candidate for discussion.
> 
And it'll open up new approaches which previously were dismissed,
like re-implementing multipathing on top of scsi-mq, giving us the
single scsi device like other UNIX systems.

Also I do think there's quite some synergy to be had, as with blk-mq
we could nail each queue to a processor, which would eliminate the
need for locking.
Which could be useful for other subsystems, too.

Cheers,

Hannes
-- 
Dr. Hannes Reinecke		      zSeries & Storage
hare@suse.de			      +49 911 74053 688
SUSE LINUX Products GmbH, Maxfeldstr. 5, 90409 Nürnberg
GF: J. Hawn, J. Guild, F. Imendörffer, HRB 16746 (AG Nürnberg)

  reply	other threads:[~2013-07-12 10:52 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-07-12  0:23 [ATTEND] scsi-mq prototype discussion Nicholas A. Bellinger
2013-07-12  1:02 ` [Ksummit-2013-discuss] " Greg KH
2013-07-12  1:33   ` Nicholas A. Bellinger
2013-07-12 10:52     ` Hannes Reinecke [this message]
2013-07-13  6:53       ` James Bottomley
2013-07-16 21:07         ` Nicholas A. Bellinger
2013-07-16 21:15           ` Jens Axboe
2013-07-17  4:52             ` James Bottomley
2013-07-19 14:01               ` Ric Wheeler
2013-07-22 16:34                 ` Jens Axboe
2013-07-19 21:22               ` Nicholas A. Bellinger
2013-07-19 21:46                 ` James Bottomley
2013-07-19 22:06                   ` Nicholas A. Bellinger
2013-07-16 22:19           ` scameron
2013-11-29 14:08 ` scsi-mq prototype Bart Van Assche
2013-12-09 21:05   ` Nicholas A. Bellinger

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=51DFDFF5.80702@suse.de \
    --to=hare@suse.de \
    --cc=James.Smart@Emulex.Com \
    --cc=andrew.vasquez@qlogic.com \
    --cc=axboe@kernel.dk \
    --cc=greg@kroah.com \
    --cc=hch@lst.de \
    --cc=jbottomley@parallels.com \
    --cc=kmo@daterainc.com \
    --cc=ksummit-2013-discuss@lists.linuxfoundation.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-scsi@vger.kernel.org \
    --cc=nab@linux-iscsi.org \
    --cc=scameron@beardog.cce.hp.com \
    --cc=target-devel@vger.kernel.org \
    --cc=tj@kernel.org \
    /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.