From: Mike Christie <michaelc@cs.wisc.edu>
To: Eddie Wai <eddie.wai@broadcom.com>
Cc: Bart Van Assche <bvanassche@acm.org>,
Peter Zijlstra <peterz@infradead.org>,
"linux-scsi@vger.kernel.org" <linux-scsi@vger.kernel.org>
Subject: Re: bnx2i kthread madness
Date: Wed, 28 Sep 2011 15:07:02 -0500 [thread overview]
Message-ID: <4E837E66.3040306@cs.wisc.edu> (raw)
In-Reply-To: <1317234379.3678.1020.camel@ltirv-waie-lx1>
On 09/28/2011 01:26 PM, Eddie Wai wrote:
>
> On Wed, 2011-09-28 at 10:33 -0700, Bart Van Assche wrote:
>> On Wed, Sep 28, 2011 at 7:29 PM, Eddie Wai <eddie.wai@broadcom.com> wrote:
>>> On Wed, 2011-09-28 at 08:05 -0700, Peter Zijlstra wrote:
>>>> I accidentally looked at all kthreads in existence on my system and
>>>> found I had:
>>>>
>>>> [iscsi_eh]
>>>> [bnx2i_thread/0]
>>>> [bnx2i_thread/1]
>>>> [bnx2i_thread/2]
>>>> [bnx2i_thread/3]
>>>> [bnx2i_thread/4]
>>>> [bnx2i_thread/5]
>>>> [bnx2i_thread/6]
>>>> [bnx2i_thread/7]
>>>> [bnx2i_thread/8]
>>>> [bnx2i_thread/9]
>>>> [bnx2i_thread/10]
>>>> [bnx2i_thread/11]
>>>> [bnx2i_thread/12]
>>>> [bnx2i_thread/13]
>>>> [bnx2i_thread/14]
>>>> [bnx2i_thread/15]
>>>> [bnx2i_thread/16]
>>>> [bnx2i_thread/17]
>>>> [bnx2i_thread/18]
>>>> [bnx2i_thread/19]
>>>> [bnx2i_thread/20]
>>>> [bnx2i_thread/21]
>>>> [bnx2i_thread/22]
>>>> [bnx2i_thread/23]
>>>>
>>>> This left me wondering why, because I most certainly am not using iSCSI.
>>>> I don't even know why its enabled in my .config (and it won't be long).
>>>>
>>>> Please fix this muck to not create useless threads.
>>>
>>> Point noted. In the current bnx2i driver, one kthread is created per
>>> cpu core upon module init (and destroyed upon module exit). The
>>> kthreads are meant only to improve I/O performance when iSCSI is
>>> employed. Otherwise, I agree that they should not exist.
>>
>> Why doesn't bnx2i use one of the system work queues defined in
>> <linux/workqueue.h> ?
> We defined our own kthreads instead is mainly because we felt that work
> queues might not have the response time we like to handle I/O
> completions under heavy stress environments as we migrated from
> tasklets. Although we really haven't yet quantified this assumption.
bnx2fc and fcoe have the same issue. qla2xxx seems to use workqueues and
is ok.
If perf is a issue then like have I said before when this patch was
submitted, and when the fcoe and bnx2fc ones were too, :) I think you
need to change blkiopoll to do what you actually want.
next prev parent reply other threads:[~2011-09-28 20:07 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-09-28 15:05 bnx2i kthread madness Peter Zijlstra
2011-09-28 17:29 ` Eddie Wai
2011-09-28 17:33 ` Bart Van Assche
2011-09-28 18:26 ` Eddie Wai
2011-09-28 20:07 ` Mike Christie [this message]
2011-09-28 17:47 ` James Bottomley
2011-09-28 18:03 ` Eddie Wai
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=4E837E66.3040306@cs.wisc.edu \
--to=michaelc@cs.wisc.edu \
--cc=bvanassche@acm.org \
--cc=eddie.wai@broadcom.com \
--cc=linux-scsi@vger.kernel.org \
--cc=peterz@infradead.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 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.