From: Bryan Schumaker <bjschuma@netapp.com>
To: "J. Bruce Fields" <bfields@fieldses.org>
Cc: "linux-nfs@vger.kernel.org" <linux-nfs@vger.kernel.org>
Subject: Re: [PATCH 2/2] lockd: Mostly remove BKL from the server
Date: Wed, 22 Sep 2010 11:43:02 -0400 [thread overview]
Message-ID: <4C9A2406.6070100@netapp.com> (raw)
In-Reply-To: <20100922153702.GD15560@fieldses.org>
On 09/22/2010 11:37 AM, J. Bruce Fields wrote:
> On Tue, Sep 21, 2010 at 04:38:12PM -0400, Bryan Schumaker wrote:
>> lockd: Mostly remove BKL from the server
>>
>> This patch removes all but one call to lock_kernel() from the server.
>
> Thanks. Does this need to go in any particular order with respect to
> the other BKL patches, or should I just apply this whenever?
>
> --b.
It doesn't use lock_flocks(), so you should be able to apply it whenever.
-Bryan
next prev parent reply other threads:[~2010-09-22 15:43 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-09-21 20:38 [PATCH 2/2] lockd: Mostly remove BKL from the server Bryan Schumaker
2010-09-22 15:37 ` J. Bruce Fields
2010-09-22 15:43 ` Bryan Schumaker [this message]
2010-09-22 15:49 ` Trond Myklebust
2010-09-22 19:14 ` J. Bruce Fields
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=4C9A2406.6070100@netapp.com \
--to=bjschuma@netapp.com \
--cc=bfields@fieldses.org \
--cc=linux-nfs@vger.kernel.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