From: Stephen Hemminger <shemminger@vyatta.com>
To: Eric Dumazet <eric.dumazet@gmail.com>
Cc: David Miller <davem@davemloft.net>, netdev@vger.kernel.org
Subject: Re: [PATCH] neigh: replace unres_qlen by unres_qlen_bytes
Date: Tue, 8 Nov 2011 17:05:42 -0800 [thread overview]
Message-ID: <20111108170542.18595c52@nehalam.linuxnetplumber.net> (raw)
In-Reply-To: <1320797656.26025.43.camel@edumazet-laptop>
On Wed, 09 Nov 2011 01:14:16 +0100
Eric Dumazet <eric.dumazet@gmail.com> wrote:
> [PATCH V2 net-next] neigh: replace unres_qlen by unres_qlen_bytes
>
> unres_qlen is the number of frames we are able to queue per unresolved
> neighbour. Its default value (3) was never changed and is responsible
> for strange drops, especially if IP fragments are used, or multiple
> sessions start in parallel. TCP initial congestion window is now bigger
> than 3.
I don't understand this argument.
TCP won't send data until the initial SYN is acked. And the SYN can't
be sent until the ARP is resolved.
The only use case for this is for applications that open lots of connections
to the same destination as once (a.k.a TCP accelerators) to get around
TCP slow start.
next prev parent reply other threads:[~2011-11-09 1:05 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
2011-11-09 0:14 ` [PATCH] neigh: replace unres_qlen by unres_qlen_bytes Eric Dumazet
2011-11-09 1:05 ` Stephen Hemminger [this message]
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=20111108170542.18595c52@nehalam.linuxnetplumber.net \
--to=shemminger@vyatta.com \
--cc=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