All of lore.kernel.org
 help / color / mirror / Atom feed
From: Sagi Grimberg <sagig@dev.mellanox.co.il>
To: Mike Snitzer <snitzer@redhat.com>, lsf-pc@lists.linux-foundation.org
Cc: linux-scsi@vger.kernel.org
Subject: Re: [LSF/MM ATTEND] interest in blk-mq, scsi-mq, dm-cache, dm-thinp, dm-*
Date: Mon, 20 Jan 2014 14:21:20 +0200	[thread overview]
Message-ID: <52DD14C0.6070403@dev.mellanox.co.il> (raw)
In-Reply-To: <52D80A0D.8090909@dev.mellanox.co.il>

On 1/16/2014 6:34 PM, Sagi Grimberg wrote:
> On 1/10/2014 8:27 PM, Mike Snitzer 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.

Sparing a few words on why I voted on this topic,
As part of me being involved in fast RDMA based initiators (iSER, SRP) I 
can say that SCSI layer
became a real performance bottleneck. Implementations bypassing SCSI has 
started to pop-up lately.
scsi-mq can and should boost performance and it is important that we 
work also on LLDs to
provide a total solution.

Sagi.

  reply	other threads:[~2014-01-20 12:21 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 [this message]
2014-01-16 22:35 ` Giridhar Malavali
2014-01-22  9:54   ` Bart Van Assche
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=52DD14C0.6070403@dev.mellanox.co.il \
    --to=sagig@dev.mellanox.co.il \
    --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.