From: Tejun Heo <tj@kernel.org>
To: "J. Bruce Fields" <bfields@fieldses.org>
Cc: Tom Tucker <tom@opengridcomputing.com>,
Trond Myklebust <Trond.Myklebust@netapp.com>,
linux-nfs@vger.kernel.org, lkml <linux-kernel@vger.kernel.org>,
Tom Tucker <tom@ogc.us>
Subject: Re: [PATCH linux-2.6.36-rc7] sunrpc/xprtrdma: clean up workqueue usage
Date: Thu, 21 Oct 2010 17:33:21 +0200 [thread overview]
Message-ID: <4CC05D41.1090207@kernel.org> (raw)
In-Reply-To: <20101021151621.GA8738@fieldses.org>
On 10/21/2010 05:16 PM, J. Bruce Fields wrote:
>> I've tested this now with iozone etc... works like a charm ;-)
>
> Applied, thanks!
Great, thank you. :-)
--
tejun
prev parent reply other threads:[~2010-10-21 15:33 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-10-15 15:49 [PATCH linux-2.6.36-rc7] sunrpc/xprtrdma: clean up workqueue usage Tejun Heo
2010-10-15 17:11 ` J. Bruce Fields
2010-10-15 17:46 ` Tom Tucker
2010-10-15 19:11 ` Tejun Heo
2010-10-20 16:05 ` Tom Tucker
2010-10-21 15:16 ` J. Bruce Fields
2010-10-21 15:33 ` Tejun Heo [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=4CC05D41.1090207@kernel.org \
--to=tj@kernel.org \
--cc=Trond.Myklebust@netapp.com \
--cc=bfields@fieldses.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-nfs@vger.kernel.org \
--cc=tom@ogc.us \
--cc=tom@opengridcomputing.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;
as well as URLs for NNTP newsgroup(s).