From: David Miller <davem@davemloft.net>
To: eric.dumazet@gmail.com
Cc: netdev@vger.kernel.org
Subject: Re: [PATCH] neigh: increase unres_qlen by one magnitude
Date: Tue, 08 Nov 2011 17:48:20 -0500 (EST) [thread overview]
Message-ID: <20111108.174820.558780148839093199.davem@davemloft.net> (raw)
In-Reply-To: <1320792301.26025.21.camel@edumazet-laptop>
From: Eric Dumazet <eric.dumazet@gmail.com>
Date: Tue, 08 Nov 2011 23:45:01 +0100
> Maybe we can do the same for unres_qlen, and setup a byte limit instead
> of 3 packets limit (say 64Kbytes of truesize per destination)
That makes sense because what typically gets blocked are initial TCP SYNs,
small UDP requests, and ICMPs.
next prev parent reply other threads:[~2011-11-08 22:48 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-11-08 20:11 [PATCH] neigh: increase unres_qlen by one magnitude Eric Dumazet
2011-11-08 22:24 ` David Miller
2011-11-08 22:45 ` Eric Dumazet
2011-11-08 22:48 ` David Miller [this message]
2011-11-09 0:14 ` [PATCH] neigh: replace unres_qlen by unres_qlen_bytes Eric Dumazet
2011-11-09 1:05 ` Stephen Hemminger
2011-11-09 5:18 ` David Miller
2011-11-09 7:55 ` Eric Dumazet
2011-11-09 11:04 ` [PATCH V3 net-next] neigh: new unresolved queue limits Eric Dumazet
2011-11-09 11:10 ` 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=20111108.174820.558780148839093199.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=eric.dumazet@gmail.com \
--cc=netdev@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