From: Jens Axboe <axboe@kernel.dk>
To: "Philip J. Kelleher" <pjk1939@linux.vnet.ibm.com>
Cc: linux-kernel@vger.kernel.org, klebers@linux.vnet.ibm.com,
brking@linux.vnet.ibm.com
Subject: Re: [PATCH 8/9] rsxx: Fixes CPU usage issues on RHEL 6 Kernels.
Date: Wed, 1 May 2013 21:35:01 +0200 [thread overview]
Message-ID: <20130501193501.GL7800@kernel.dk> (raw)
In-Reply-To: <20130501143449.GB17546@oc6784271780.ibm.com>
On Wed, May 01 2013, Philip J. Kelleher wrote:
> Again, thanks for the prompt reply.
>
> Also, sorry for my poor explaination skills :)
>
> The RHEL 6.x version of the driver is using the legacy
> worqueue create function, 'create_singlethread_workqueue'.
> This would cause heavy usage of one CPU if data was being
> thrashed pretty hard. So, in order to fix it, workqueues
> are now being created with 'create_workqueue' and
> synchronization with mutexes.
See, that is what should have been in the changelog!
--
Jens Axboe
prev parent reply other threads:[~2013-05-01 19:35 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-04-30 20:00 [PATCH 8/9] rsxx: Fixes CPU usage issues on RHEL 6 Kernels Philip J. Kelleher
2013-05-01 11:44 ` Jens Axboe
2013-05-01 14:34 ` Philip J. Kelleher
2013-05-01 19:35 ` Jens Axboe [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=20130501193501.GL7800@kernel.dk \
--to=axboe@kernel.dk \
--cc=brking@linux.vnet.ibm.com \
--cc=klebers@linux.vnet.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=pjk1939@linux.vnet.ibm.com \
/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