Bug#699361: linux-image-3.2.0-0.bpo.4-amd64: nfsd4 RELEASE_LOCKOWNER is slow and, CPU intensive
On 19/03/13 04:13, Ben Hutchings wrote:
> That's good, but I wonder whether this might also needed:
>
> commit 009673b439cf74d70a486fca0177e274febd81a7
> Author: J. Bruce Fields <bfields@redhat.com>
> Date: Mon Nov 7 17:40:10 2011 -0500
[snip]
> (That might also depend on:
>
> commit 16bfdaafa2c66d8cc81422a97a105a849ca65b3e
> Author: J. Bruce Fields <bfields@redhat.com>
> Date: Mon Nov 7 17:23:30 2011 -0500
>
[snip]
>
> though I think they're independent.)
>
> Ben.
We've been running a custom kernel based on
linux-image-3.2.0-0.bpo.4-amd64 3.2.39-2~bpo60+1 with the following
patches applied:
06f1f864d4ae5804e83785308d41f14a08e4b980
[PATCH] nfsd4: hash lockowners to simplify RELEASE_LOCKOWNER
64a284d07c7d84299a90826950079a8ef11e8204
[PATCH 1/1] nfsd4: maintain one seqid stream per (lockowner, file)
This list does not include the two patches you suggested above. For us,
the two patches we have applied have completely fixed the problems we
were experiencing, and the system has been stable for nearly 3 weeks now.
Please consider adding those patches to the Wheezy kernel (admittedly
they probably won't make it now, or at least not until the next point
release).
Best regards,
Chris
--
|Chris Boot
|Tiger Computing Ltd
|"Linux for Business"
|
|Tel: 033 0088 1511
|Web: http://www.tiger-computing.co.uk
|
|Registered in England. Company number: 3389961
|Registered address: Wyastone Business Park,
| Wyastone Leys, Monmouth, NP25 3SR
Reply to: