From: David Miller <davem@davemloft.net>
To: yi.zhu@intel.com
Cc: netdev@vger.kernel.org, alex.shi@intel.com
Subject: Re: [RFC PATCH] accounting for socket backlog
Date: Thu, 25 Feb 2010 21:52:48 -0800 (PST) [thread overview]
Message-ID: <20100225.215248.29533524.davem@davemloft.net> (raw)
In-Reply-To: <1267152253.16986.1655.camel@debian>
From: Zhu Yi <yi.zhu@intel.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.
next prev parent reply other threads:[~2010-02-26 5:52 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-02-25 3:13 [RFC PATCH] accounting for socket backlog Zhu Yi
2010-02-25 8:31 ` David Miller
2010-02-26 2:44 ` Zhu Yi
2010-02-26 5:52 ` David Miller [this message]
2010-02-25 11:24 ` Eric Dumazet
2010-02-26 2:34 ` Zhu Yi
2010-02-26 13:12 ` Eric Dumazet
2010-03-01 2:17 ` Zhu Yi
2010-03-01 2:29 ` Eric Dumazet
2010-03-01 3:03 ` Zhu Yi
2010-03-01 3:12 ` Eric Dumazet
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=20100225.215248.29533524.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=alex.shi@intel.com \
--cc=netdev@vger.kernel.org \
--cc=yi.zhu@intel.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).