netdev - Re: [RFC PATCH] accounting for socket backlog

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-Id: <20100225.215248.29533524.davem@davemloft.net>
Date:	Thu, 25 Feb 2010 21:52:48 -0800 (PST)
From:	David Miller <davem@...emloft.net>
To:	yi.zhu@...el.com
Cc:	netdev@...r.kernel.org, alex.shi@...el.com
Subject: Re: [RFC PATCH] accounting for socket backlog

From: Zhu Yi <yi.zhu@...el.com>
Date: Fri, 26 Feb 2010 10:44:13 +0800

> On Thu, 2010-02-25 at 16:31 +0800, David Miller wrote:
>> Right now we can queue up a lot and still get it to the application
>> if it is slow getting scheduled onto a cpu, but if you put this
>> limit here it could result in lots of drops. 
> 
> Or we can replace the sk->sk_rcvbuf limit with a backlog own limit. We
> can queue "a lot", but not endless. We have to have a limit anyway.

Simply using (2 * sk->sk_rcvbuf) might be sufficient enough.
--
To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html