From: James Smart <james.smart@emulex.com>
To: James Bottomley <James.Bottomley@HansenPartnership.com>
Cc: "Nicholas A. Bellinger" <nab@linux-iscsi.org>,
lsf-pc@lists.linux-foundation.org,
linux-scsi <linux-scsi@vger.kernel.org>,
LKML <linux-kernel@vger.kernel.org>
Subject: Re: [LSF/MM TOPIC] [ATTEND] scsi-mq
Date: Wed, 22 Jan 2014 14:02:02 -0500 [thread overview]
Message-ID: <52E015AA.6010104@emulex.com> (raw)
In-Reply-To: <52D808FD.9010007@dev.mellanox.co.il>
James,
I'd like to attend to participate in the EH, MQ, and T10 PI RDMA
discussions.
-- james s
On 1/16/2014 11:29 AM, Sagi Grimberg wrote:
> On 1/16/2014 1:05 AM, Nicholas A. Bellinger wrote:
>> Hi all,
>>
>> I'd like to discuss the current state of scsi-mq prototype code.
>>
>> And now that blk-mq is upstream for v3.13, exploring the remaining TODO
>> items towards an initial scsi-mq merge sometime before 2015 is upon us.
>>
>> The benefits of scsi-mq remain unchanged:
>>
>> - Utilizes blk-mq's native per-cpu primitive + NUMA local friendly
>> queuing of pre-allocated struct request descriptor memory
>> - Eliminates all fast-path memory allocations in SCSI-core +
>> optionally the underlying SCSI LLDs
>> - Avoids fast-path Scsi_Host->host_lock + request_queue->queue_lock
>> accesses in submission + completion paths
>>
>> These benefits have been discussed in greater detail in [1], and the
>> latest alpha quality code is available at [2] below.
>>
>> The current TODO items include:
>>
>> - A plan for per device SCSI error handling
>> - Proper scsi_device->sdev_gendev reference counting
>> - Queuing fairness across multiple scsi-mq devices per host
>> - Support for > 1 nr_hw_queues + conversion of qla2xxx + lpfc
>> LLDs that support native hardware multiqueue
>>
>> Thank you,
>>
>> --nab
>>
>> References:
>>
>> [1]:
>> [ATTEND] scsi-mq prototype discussion
>> http://marc.info/?l=linux-scsi&m=137358831329753&w=2
>>
>> [2]:
>> scsi-mq WIP updated to v3.13-rc3
>> http://marc.info/?l=linux-scsi&m=138782535731722&w=2
>>
>
> +1
> I would be happy to join this discussion, I think it is also important
> to think about the interaction with iSCSI and LLDs.
>
> Sagi.
>
> --
> To unsubscribe from this list: send the line "unsubscribe linux-scsi" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
>
>
WARNING: multiple messages have this Message-ID (diff)
From: James Smart <james.smart@emulex.com>
To: James Bottomley <James.Bottomley@HansenPartnership.com>
Cc: "Nicholas A. Bellinger" <nab@linux-iscsi.org>,
<lsf-pc@lists.linux-foundation.org>,
linux-scsi <linux-scsi@vger.kernel.org>,
LKML <linux-kernel@vger.kernel.org>
Subject: Re: [LSF/MM TOPIC] [ATTEND] scsi-mq
Date: Wed, 22 Jan 2014 14:02:02 -0500 [thread overview]
Message-ID: <52E015AA.6010104@emulex.com> (raw)
In-Reply-To: <52D808FD.9010007@dev.mellanox.co.il>
James,
I'd like to attend to participate in the EH, MQ, and T10 PI RDMA
discussions.
-- james s
On 1/16/2014 11:29 AM, Sagi Grimberg wrote:
> On 1/16/2014 1:05 AM, Nicholas A. Bellinger wrote:
>> Hi all,
>>
>> I'd like to discuss the current state of scsi-mq prototype code.
>>
>> And now that blk-mq is upstream for v3.13, exploring the remaining TODO
>> items towards an initial scsi-mq merge sometime before 2015 is upon us.
>>
>> The benefits of scsi-mq remain unchanged:
>>
>> - Utilizes blk-mq's native per-cpu primitive + NUMA local friendly
>> queuing of pre-allocated struct request descriptor memory
>> - Eliminates all fast-path memory allocations in SCSI-core +
>> optionally the underlying SCSI LLDs
>> - Avoids fast-path Scsi_Host->host_lock + request_queue->queue_lock
>> accesses in submission + completion paths
>>
>> These benefits have been discussed in greater detail in [1], and the
>> latest alpha quality code is available at [2] below.
>>
>> The current TODO items include:
>>
>> - A plan for per device SCSI error handling
>> - Proper scsi_device->sdev_gendev reference counting
>> - Queuing fairness across multiple scsi-mq devices per host
>> - Support for > 1 nr_hw_queues + conversion of qla2xxx + lpfc
>> LLDs that support native hardware multiqueue
>>
>> Thank you,
>>
>> --nab
>>
>> References:
>>
>> [1]:
>> [ATTEND] scsi-mq prototype discussion
>> http://marc.info/?l=linux-scsi&m=137358831329753&w=2
>>
>> [2]:
>> scsi-mq WIP updated to v3.13-rc3
>> http://marc.info/?l=linux-scsi&m=138782535731722&w=2
>>
>
> +1
> I would be happy to join this discussion, I think it is also important
> to think about the interaction with iSCSI and LLDs.
>
> Sagi.
>
> --
> To unsubscribe from this list: send the line "unsubscribe linux-scsi" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
>
>
next prev parent reply other threads:[~2014-01-22 19:02 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-01-15 23:05 [LSF/MM TOPIC] [ATTEND] scsi-mq Nicholas A. Bellinger
2014-01-16 16:29 ` Sagi Grimberg
2014-01-22 19:02 ` James Smart [this message]
2014-01-22 19:02 ` James Smart
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=52E015AA.6010104@emulex.com \
--to=james.smart@emulex.com \
--cc=James.Bottomley@HansenPartnership.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-scsi@vger.kernel.org \
--cc=lsf-pc@lists.linux-foundation.org \
--cc=nab@linux-iscsi.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.