All of lore.kernel.org
 help / color / mirror / Atom feed
From: Sebastian Andrzej Siewior <bigeasy@linutronix.de>
To: linux-scsi@vger.kernel.org, Christoph Hellwig <hch@lst.de>
Cc: jth@kernel.org, rt@linutronix.de, jejb@linux.vnet.ibm.com,
	"Martin K . Petersen" <martin.petersen@oracle.com>,
	QLogic-Storage-Upstream@qlogic.com
Subject: Re: [PATCH 1/4] scsi: bnx2fc: convert per-CPU thread to kworker
Date: Fri, 12 Aug 2016 13:00:27 +0200	[thread overview]
Message-ID: <20160812110026.2aluranpmwejxn6h@linutronix.de> (raw)
In-Reply-To: <1467734929-24442-1-git-send-email-bigeasy@linutronix.de>

On 2016-07-05 18:08:46 [+0200], To linux-scsi@vger.kernel.org wrote:
> The driver creates its own per-CPU threads which are updated based on CPU
> hotplug events. It is also possible to use kworkers and remove some of the
> infrastructure get the same job done while saving a few lines of code.

ping

Sebastian

      parent reply	other threads:[~2016-08-12 11:00 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-07-05 16:08 [PATCH 1/4] scsi: bnx2fc: convert per-CPU thread to kworker Sebastian Andrzej Siewior
2016-07-05 16:08 ` [PATCH 2/4] scsi: bnx2fc: clean up header definitions Sebastian Andrzej Siewior
2016-07-05 16:08 ` [PATCH 3/4] scsi: bnx2fc: annoate unlock + release for sparse Sebastian Andrzej Siewior
2016-07-05 16:08 ` [PATCH 4/4] scsi: bnx2fc: convert bnx2fc_l2_rcv_thread() to worker Sebastian Andrzej Siewior
2016-07-05 16:20   ` [PATCH 4/4 v2] " Sebastian Andrzej Siewior
2016-07-20 11:04 ` [PATCH 1/4] scsi: bnx2fc: convert per-CPU thread to kworker Johannes Thumshirn
2016-07-20 12:07   ` Sebastian Andrzej Siewior
2016-07-20 12:13     ` Johannes Thumshirn
2016-08-12 11:00 ` Sebastian Andrzej Siewior [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=20160812110026.2aluranpmwejxn6h@linutronix.de \
    --to=bigeasy@linutronix.de \
    --cc=QLogic-Storage-Upstream@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 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.