From: "Martin K. Petersen" <martin.petersen@oracle.com>
To: Daniel Wagner <wagi@monom.org>
Cc: linux-scsi@vger.kernel.org,
"James E.J. Bottomley" <jejb@linux.vnet.ibm.com>,
"Martin K. Petersen" <martin.petersen@oracle.com>,
Matthew Wilcox <matthew.r.wilcox@intel.com>,
linux-kernel@vger.kernel.org,
Daniel Wagner <daniel.wagner@bmw-carit.de>
Subject: Re: [PATCH 0/3] wireless: Use complete() instead complete_all()
Date: Wed, 14 Sep 2016 13:23:46 -0400 [thread overview]
Message-ID: <yq17faemm3h.fsf@sermon.lab.mkp.net> (raw)
In-Reply-To: <1473757130-14751-1-git-send-email-wagi@monom.org> (Daniel Wagner's message of "Tue, 13 Sep 2016 10:58:47 +0200")
>>>>> "Daniel" == Daniel Wagner <wagi@monom.org> writes:
Daniel> Using complete_all() is not wrong per se but it suggest that
Daniel> there might be more than one waiter. For -rt I am reviewing all
Daniel> complete_all() users and would like to leave only the real ones
Daniel> in the tree. The main problem for -rt about complete_all() is
Daniel> that it can be uses inside IRQ context and that can lead to
Daniel> unbounded amount work inside the interrupt handler. That is a no
Daniel> no for -rt.
Daniel> The patches grouped per subsystem and in small batches to allow
Daniel> reviewing.
Applied to 4.9/scsi-queue.
--
Martin K. Petersen Oracle Linux Engineering
prev parent reply other threads:[~2016-09-14 17:24 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-09-13 8:58 [PATCH 0/3] wireless: Use complete() instead complete_all() Daniel Wagner
2016-09-13 8:58 ` [PATCH 1/3] csiostor: fix completion usage Daniel Wagner
2016-09-14 7:26 ` Christoph Hellwig
2016-09-13 8:58 ` [PATCH 2/3] sym53c8xx_2: use complete() instead complete_all() Daniel Wagner
2016-09-14 7:26 ` Christoph Hellwig
2016-09-13 8:58 ` [PATCH 3/3] virtio_scsi: " Daniel Wagner
2016-09-14 7:27 ` Christoph Hellwig
2016-09-14 17:23 ` Martin K. Petersen [this message]
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=yq17faemm3h.fsf@sermon.lab.mkp.net \
--to=martin.petersen@oracle.com \
--cc=daniel.wagner@bmw-carit.de \
--cc=jejb@linux.vnet.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-scsi@vger.kernel.org \
--cc=matthew.r.wilcox@intel.com \
--cc=wagi@monom.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox