All of lore.kernel.org
 help / color / mirror / Atom feed
From: Christoph Hellwig <hch@infradead.org>
To: Bart Van Assche <bart.vanassche@sandisk.com>
Cc: "lsf-pc@lists.linux-foundation.org"
	<lsf-pc@lists.linux-foundation.org>,
	Christoph Hellwig <hch@infradead.org>,
	Mike Snitzer <snitzer@redhat.com>,
	"linux-scsi@vger.kernel.org" <linux-scsi@vger.kernel.org>
Subject: Re: [Lsf-pc] [LSF/MM TOPIC] How SRP initiator performance has been improved via scsi-mq
Date: Thu, 15 Jan 2015 01:15:21 -0800	[thread overview]
Message-ID: <20150115091521.GA3360@infradead.org> (raw)
In-Reply-To: <54B638E3.3030406@sandisk.com>

On Wed, Jan 14, 2015 at 10:37:39AM +0100, Bart Van Assche wrote:
> Recently it has been proposed to discuss how to add scsi-mq support in
> the iSER initiator during the 2015 edition of the LSF/MM summit. In the
> discussion that followed that proposal several questions were asked
> about how scsi-mq support has been added in the SRP initiator driver,
> which design choices have been made and which lessons have been learned.
> Hence the proposal to add a topic to the LSF/MM schedule for reporting
> how scsi-mq support has been added in the SRP initiator.
> 
> For the actual discussion see also Sagi Grimberg, [LSF/MM TOPIC] iSCSI
> MQ adoption via MCS discussion, linux-scsi mailing list, January 7, 2015
> (http://thread.gmane.org/gmane.linux.scsi/98199).
> 
> Christoph and Mike, if you would like to complement this topic with a
> presentation about the scsi-mq core itself and/or integration of
> multiqueue support in the device mapper multipath driver, I would
> welcome this.

A big long blk-mq / scsi-mq sessions sounds like a good plan.  That
can include a brief overview of the existing work and all the
still pending bits for iSCSI/iSER, multipath and so on.

      reply	other threads:[~2015-01-15  9:15 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-01-14  9:37 [LSF/MM TOPIC] How SRP initiator performance has been improved via scsi-mq Bart Van Assche
2015-01-15  9:15 ` Christoph Hellwig [this message]

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=20150115091521.GA3360@infradead.org \
    --to=hch@infradead.org \
    --cc=bart.vanassche@sandisk.com \
    --cc=linux-scsi@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 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.