From: Christoph Hellwig <hch@infradead.org>
To: Sebastian Andrzej Siewior <bigeasy@linutronix.de>
Cc: linux-scsi@vger.kernel.org, Johannes Thumshirn <jth@kernel.org>,
rt@linutronix.de,
"James E.J. Bottomley" <jejb@linux.vnet.ibm.com>,
"Martin K. Petersen" <martin.petersen@oracle.com>,
QLogic-Storage-Upstream@qlogic.com,
Christoph Hellwig <hch@lst.de>,
Chad Dupuis <chad.dupuis@qlogic.com>
Subject: Re: [REPOST PATCH 1/5] scsi: bnx2i: convert to kworker
Date: Mon, 7 Nov 2016 08:19:01 -0800 [thread overview]
Message-ID: <20161107161901.GA12297@infradead.org> (raw)
In-Reply-To: <20160817101003.30055-1-bigeasy@linutronix.de>
It seems like the whole damn driver should just use threaded interrupts.
Of course it's a giant beast and not just the iSCSI one. But even
if we don't go all the way I'd much prefer workqueues. kthread work
is simply the worst API ever and I'd prefer to not have it proliferate.
next prev parent reply other threads:[~2016-11-07 16:19 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-08-17 10:09 [REPOST PATCH 1/5] scsi: bnx2i: convert to kworker Sebastian Andrzej Siewior
2016-08-17 10:10 ` [REPOST PATCH 2/5] scsi: bnx2fc: convert per-CPU thread " Sebastian Andrzej Siewior
2016-08-17 10:10 ` [REPOST PATCH 3/5] scsi: bnx2fc: clean up header definitions Sebastian Andrzej Siewior
2016-08-17 10:10 ` [REPOST PATCH 4/5] scsi: bnx2fc: annoate unlock + release for sparse Sebastian Andrzej Siewior
2016-08-17 10:10 ` [REPOST PATCH 5/5] scsi: bnx2fc: convert bnx2fc_l2_rcv_thread() to worker Sebastian Andrzej Siewior
2016-09-08 12:39 ` [REPOST PATCH 1/5] scsi: bnx2i: convert to kworker Johannes Thumshirn
2016-09-09 11:28 ` Martin K. Petersen
2016-09-13 13:28 ` Chad Dupuis
2016-09-14 17:25 ` Martin K. Petersen
2016-09-30 21:43 ` Sebastian Andrzej Siewior
2016-11-07 16:19 ` Christoph Hellwig [this message]
2016-11-07 16:31 ` [PREEMPT-RT] " Thomas Gleixner
2016-11-07 16:38 ` Christoph Hellwig
2016-11-07 16:46 ` Sebastian Andrzej Siewior
2016-11-07 16:48 ` Christoph Hellwig
2016-11-07 17:04 ` Sebastian Andrzej Siewior
2016-11-07 19:10 ` Christoph Hellwig
2016-11-08 7:24 ` Johannes Thumshirn
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=20161107161901.GA12297@infradead.org \
--to=hch@infradead.org \
--cc=QLogic-Storage-Upstream@qlogic.com \
--cc=bigeasy@linutronix.de \
--cc=chad.dupuis@qlogic.com \
--cc=hch@lst.de \
--cc=jejb@linux.vnet.ibm.com \
--cc=jth@kernel.org \
--cc=linux-scsi@vger.kernel.org \
--cc=martin.petersen@oracle.com \
--cc=rt@linutronix.de \
/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).