From: Johannes Thumshirn <jthumshirn@suse.de>
To: "lsf-pc@lists.linux-foundation.org" <lsf-pc@lists.linux-foundation.org>
Cc: linux-block@vger.kernel.org, Linux-scsi@vger.kernel.org,
Sagi Grimberg <sagi@grimberg.me>,
linux-nvme@lists.infradead.org,
Christoph Hellwig <hch@infradead.org>,
Keith Busch <keith.busch@intel.com>
Subject: [LSF/MM TOPIC][LSF/MM ATTEND] NAPI polling for block drivers
Date: Wed, 11 Jan 2017 14:43:12 +0100 [thread overview]
Message-ID: <20170111134312.GH6286@linux-x5ow.site> (raw)
Hi all,
I'd like to attend LSF/MM and would like to discuss polling for block drivers.
Currently there is blk-iopoll but it is neither as widely used as NAPI in the
networking field and accoring to Sagi's findings in [1] performance with
polling is not on par with IRQ usage.
On LSF/MM I'd like to whether it is desirable to have NAPI like polling in
more block drivers and how to overcome the currently seen performance issues.
[1] http://lists.infradead.org/pipermail/linux-nvme/2016-October/006975.html
Byte,
Johannes
--
Johannes Thumshirn Storage
jthumshirn@suse.de +49 911 74053 689
SUSE LINUX GmbH, Maxfeldstr. 5, 90409 N�rnberg
GF: Felix Imend�rffer, Jane Smithard, Graham Norton
HRB 21284 (AG N�rnberg)
Key fingerprint = EC38 9CAB C2C4 F25D 8600 D0D0 0393 969D 2D76 0850
WARNING: multiple messages have this Message-ID (diff)
From: jthumshirn@suse.de (Johannes Thumshirn)
Subject: [LSF/MM TOPIC][LSF/MM ATTEND] NAPI polling for block drivers
Date: Wed, 11 Jan 2017 14:43:12 +0100 [thread overview]
Message-ID: <20170111134312.GH6286@linux-x5ow.site> (raw)
Hi all,
I'd like to attend LSF/MM and would like to discuss polling for block drivers.
Currently there is blk-iopoll but it is neither as widely used as NAPI in the
networking field and accoring to Sagi's findings in [1] performance with
polling is not on par with IRQ usage.
On LSF/MM I'd like to whether it is desirable to have NAPI like polling in
more block drivers and how to overcome the currently seen performance issues.
[1] http://lists.infradead.org/pipermail/linux-nvme/2016-October/006975.html
Byte,
Johannes
--
Johannes Thumshirn Storage
jthumshirn at suse.de +49 911 74053 689
SUSE LINUX GmbH, Maxfeldstr. 5, 90409 N?rnberg
GF: Felix Imend?rffer, Jane Smithard, Graham Norton
HRB 21284 (AG N?rnberg)
Key fingerprint = EC38 9CAB C2C4 F25D 8600 D0D0 0393 969D 2D76 0850
WARNING: multiple messages have this Message-ID (diff)
From: Johannes Thumshirn <jthumshirn@suse.de>
To: "lsf-pc@lists.linux-foundation.org" <lsf-pc@lists.linux-foundation.org>
Cc: linux-block@vger.kernel.org, Linux-scsi@vger.kernel.org,
Sagi Grimberg <sagi@grimberg.me>,
linux-nvme@lists.infradead.org,
Christoph Hellwig <hch@infradead.org>,
Keith Busch <keith.busch@intel.com>
Subject: [LSF/MM TOPIC][LSF/MM ATTEND] NAPI polling for block drivers
Date: Wed, 11 Jan 2017 14:43:12 +0100 [thread overview]
Message-ID: <20170111134312.GH6286@linux-x5ow.site> (raw)
Hi all,
I'd like to attend LSF/MM and would like to discuss polling for block drivers.
Currently there is blk-iopoll but it is neither as widely used as NAPI in the
networking field and accoring to Sagi's findings in [1] performance with
polling is not on par with IRQ usage.
On LSF/MM I'd like to whether it is desirable to have NAPI like polling in
more block drivers and how to overcome the currently seen performance issues.
[1] http://lists.infradead.org/pipermail/linux-nvme/2016-October/006975.html
Byte,
Johannes
--
Johannes Thumshirn Storage
jthumshirn@suse.de +49 911 74053 689
SUSE LINUX GmbH, Maxfeldstr. 5, 90409 Nürnberg
GF: Felix Imendörffer, Jane Smithard, Graham Norton
HRB 21284 (AG Nürnberg)
Key fingerprint = EC38 9CAB C2C4 F25D 8600 D0D0 0393 969D 2D76 0850
next reply other threads:[~2017-01-11 13:43 UTC|newest]
Thread overview: 120+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-01-11 13:43 Johannes Thumshirn [this message]
2017-01-11 13:43 ` [LSF/MM TOPIC][LSF/MM ATTEND] NAPI polling for block drivers Johannes Thumshirn
2017-01-11 13:43 ` Johannes Thumshirn
2017-01-11 13:46 ` Hannes Reinecke
2017-01-11 13:46 ` Hannes Reinecke
2017-01-11 13:46 ` Hannes Reinecke
2017-01-11 15:07 ` Jens Axboe
2017-01-11 15:07 ` Jens Axboe
2017-01-11 15:13 ` Jens Axboe
2017-01-11 15:13 ` Jens Axboe
2017-01-12 8:23 ` Sagi Grimberg
2017-01-12 8:23 ` Sagi Grimberg
2017-01-12 10:02 ` Johannes Thumshirn
2017-01-12 10:02 ` Johannes Thumshirn
2017-01-12 10:02 ` Johannes Thumshirn
2017-01-12 11:44 ` Sagi Grimberg
2017-01-12 11:44 ` Sagi Grimberg
2017-01-12 12:53 ` Johannes Thumshirn
2017-01-12 12:53 ` Johannes Thumshirn
2017-01-12 12:53 ` Johannes Thumshirn
2017-01-12 14:41 ` [Lsf-pc] " Sagi Grimberg
2017-01-12 14:41 ` Sagi Grimberg
2017-01-12 18:59 ` Johannes Thumshirn
2017-01-12 18:59 ` Johannes Thumshirn
2017-01-12 18:59 ` Johannes Thumshirn
2017-01-17 15:38 ` Sagi Grimberg
2017-01-17 15:38 ` Sagi Grimberg
2017-01-17 15:45 ` Sagi Grimberg
2017-01-17 15:45 ` Sagi Grimberg
2017-01-20 12:22 ` Johannes Thumshirn
2017-01-20 12:22 ` Johannes Thumshirn
2017-01-20 12:22 ` Johannes Thumshirn
2017-01-17 16:15 ` Sagi Grimberg
2017-01-17 16:15 ` Sagi Grimberg
2017-01-17 16:27 ` Johannes Thumshirn
2017-01-17 16:27 ` Johannes Thumshirn
2017-01-17 16:27 ` Johannes Thumshirn
2017-01-17 16:38 ` Sagi Grimberg
2017-01-17 16:38 ` Sagi Grimberg
2017-01-18 13:51 ` Johannes Thumshirn
2017-01-18 13:51 ` Johannes Thumshirn
2017-01-18 13:51 ` Johannes Thumshirn
2017-01-18 14:27 ` Sagi Grimberg
2017-01-18 14:27 ` Sagi Grimberg
2017-01-18 14:36 ` Andrey Kuzmin
2017-01-18 14:36 ` Andrey Kuzmin
2017-01-18 14:40 ` Sagi Grimberg
2017-01-18 14:40 ` Sagi Grimberg
2017-01-18 15:35 ` Andrey Kuzmin
2017-01-18 15:35 ` Andrey Kuzmin
2017-01-18 14:58 ` Johannes Thumshirn
2017-01-18 14:58 ` Johannes Thumshirn
2017-01-18 14:58 ` Johannes Thumshirn
2017-01-18 15:14 ` Sagi Grimberg
2017-01-18 15:14 ` Sagi Grimberg
2017-01-18 15:16 ` Johannes Thumshirn
2017-01-18 15:16 ` Johannes Thumshirn
2017-01-18 15:16 ` Johannes Thumshirn
2017-01-18 15:39 ` Hannes Reinecke
2017-01-18 15:39 ` Hannes Reinecke
2017-01-18 15:39 ` Hannes Reinecke
2017-01-19 8:12 ` Sagi Grimberg
2017-01-19 8:12 ` Sagi Grimberg
2017-01-19 8:23 ` Sagi Grimberg
2017-01-19 8:23 ` Sagi Grimberg
2017-01-19 9:18 ` Johannes Thumshirn
2017-01-19 9:18 ` Johannes Thumshirn
2017-01-19 9:18 ` Johannes Thumshirn
2017-01-19 9:13 ` Johannes Thumshirn
2017-01-19 9:13 ` Johannes Thumshirn
2017-01-19 9:13 ` Johannes Thumshirn
2017-01-17 16:44 ` Andrey Kuzmin
2017-01-17 16:50 ` Sagi Grimberg
2017-01-17 16:50 ` Sagi Grimberg
2017-01-18 14:02 ` Hannes Reinecke
2017-01-18 14:02 ` Hannes Reinecke
2017-01-20 0:13 ` Jens Axboe
2017-01-20 0:13 ` Jens Axboe
2017-01-13 15:56 ` Johannes Thumshirn
2017-01-13 15:56 ` Johannes Thumshirn
2017-01-13 15:56 ` Johannes Thumshirn
2017-01-11 15:16 ` Hannes Reinecke
2017-01-11 15:16 ` Hannes Reinecke
2017-01-11 15:16 ` Hannes Reinecke
2017-01-12 4:36 ` Stephen Bates
2017-01-12 4:44 ` Jens Axboe
2017-01-12 4:44 ` Jens Axboe
2017-01-12 4:56 ` Stephen Bates
2017-01-12 4:56 ` Stephen Bates
2017-01-19 10:57 ` Ming Lei
2017-01-19 10:57 ` Ming Lei
2017-01-19 11:03 ` Hannes Reinecke
2017-01-19 11:03 ` Hannes Reinecke
2017-01-11 16:08 ` Bart Van Assche
2017-01-11 16:08 ` Bart Van Assche
2017-01-11 16:08 ` Bart Van Assche
2017-01-11 16:12 ` hch
2017-01-11 16:12 ` hch
2017-01-11 16:15 ` Jens Axboe
2017-01-11 16:15 ` Jens Axboe
2017-01-11 16:22 ` Hannes Reinecke
2017-01-11 16:22 ` Hannes Reinecke
2017-01-11 16:22 ` Hannes Reinecke
2017-01-11 16:26 ` Bart Van Assche
2017-01-11 16:26 ` Bart Van Assche
2017-01-11 16:26 ` Bart Van Assche
2017-01-11 16:45 ` Hannes Reinecke
2017-01-11 16:45 ` Hannes Reinecke
2017-01-11 16:45 ` Hannes Reinecke
2017-01-12 8:52 ` sagi grimberg
2017-01-12 8:52 ` sagi grimberg
2017-01-11 16:14 ` Johannes Thumshirn
2017-01-11 16:14 ` Johannes Thumshirn
2017-01-11 16:14 ` Johannes Thumshirn
2017-01-12 8:41 ` Sagi Grimberg
2017-01-12 8:41 ` Sagi Grimberg
2017-01-12 8:41 ` Sagi Grimberg
2017-01-12 19:13 ` Bart Van Assche
2017-01-12 19:13 ` Bart Van Assche
2017-01-12 19:13 ` Bart Van Assche
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=20170111134312.GH6286@linux-x5ow.site \
--to=jthumshirn@suse.de \
--cc=Linux-scsi@vger.kernel.org \
--cc=hch@infradead.org \
--cc=keith.busch@intel.com \
--cc=linux-block@vger.kernel.org \
--cc=linux-nvme@lists.infradead.org \
--cc=lsf-pc@lists.linux-foundation.org \
--cc=sagi@grimberg.me \
/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.