Re: [PATCHv 2] tcp: properly initialize tcp memory limits part 2(fix nfs regression)

From: Jason Wang
Date: Mon Mar 05 2012 - 22:22:48 EST


On 03/06/2012 02:22 AM, Sergei Trofimovich wrote:
This one looks small to me, as the tcp_{r,w}mem were count by bytes and
> limit were count by number of pages, so we need to shift PAGE_SHIFT.
> > As I can't reproduce this locally, in order to narrow down the problem,
> could you please help to check whether the issue were
> introduced/eliminated by commit 4acb4190 or 3dc43e3?
I didn't think of server problem. I did run 3.3-rc0 kernel there
from the kvm tree (v3.2-10396-g05ef4c6):
commit 05ef4c60568ed1740f65bf66a76da30b19060119
Author: Michael S. Tsirkin<mst@xxxxxxxxxx>
Date: Wed Jan 18 20:07:09 2012 +0200

kvm: fix error handling for out of range irq

from git://git.kernel.org/pub/scm/virt/kvm/kvm.git

Updating to current vanilla 3.3-rc6 solved the problem.
Are you interested in digging that issue further to find commit
breaking the server?
Hi Sergei:

So it's very possible that it's a bug which is blacklisted by early commits and uncovered by my commit ( c43b874d5d714f271b80d4c3f49e05d0cbf51ed2). I wish I can help in nfs debugging, but I'm not familiar with that.

thanks
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/