From: Bart Van Assche <bvanassche@acm.org>
To: Giridhar Malavali <giridhar.malavali@qlogic.com>,
Mike Snitzer <snitzer@redhat.com>
Cc: linux-scsi <linux-scsi@vger.kernel.org>
Subject: Re: [LSF/MM ATTEND] interest in blk-mq, scsi-mq, dm-cache, dm-thinp, dm-*
Date: Wed, 22 Jan 2014 10:54:01 +0100 [thread overview]
Message-ID: <52DF9539.9060206@acm.org> (raw)
In-Reply-To: <D63B9804CB63AD4FAAD966037695664647023F7E@avmb2.qlogic.org>
On 01/16/14 23:35, Giridhar Malavali wrote:
> On 1/10/14 10:27 AM, "Mike Snitzer" <snitzer@redhat.com> wrote:
>> I would like to attend to participate in discussions related to topics
>> listed in the subject. As a maintainer of DM I'd be interested to
>> learn/discuss areas that should become a development focus in the months
>> following LSF.
>
> +1 for scsi-mq.
(removed lsf-pc from CC-list)
Hello Giridhar,
I definitely appreciate QLogic's continuous efforts to improve
performance of their initiator and target drivers. Via your e-mail I
learned that QLogic is looking at scsi-mq, which is great news. However,
the following issue might have to be addressed before the qla2xxx driver
can fully take advantage of the scsi-mq work:
https://bugzilla.kernel.org/show_bug.cgi?id=69201. It would be
appreciated if someone could have a look at the measurements described
in that bugzilla entry.
Thanks,
Bart.
next prev parent reply other threads:[~2014-01-22 9:54 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-01-10 18:27 [LSF/MM ATTEND] interest in blk-mq, scsi-mq, dm-cache, dm-thinp, dm-* Mike Snitzer
2014-01-13 11:36 ` Hannes Reinecke
2014-01-24 2:37 ` Mike Christie
2014-01-24 7:12 ` Hannes Reinecke
2014-01-24 20:19 ` Mike Christie
2014-01-15 23:11 ` Nicholas A. Bellinger
2014-01-16 16:34 ` Sagi Grimberg
2014-01-20 12:21 ` Sagi Grimberg
2014-01-16 22:35 ` Giridhar Malavali
2014-01-22 9:54 ` Bart Van Assche [this message]
2014-01-23 1:13 ` Giridhar Malavali
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=52DF9539.9060206@acm.org \
--to=bvanassche@acm.org \
--cc=giridhar.malavali@qlogic.com \
--cc=linux-scsi@vger.kernel.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;
as well as URLs for NNTP newsgroup(s).