From: Eric Dumazet <eric.dumazet@gmail.com>
To: Vijay Subramanian <subramanian.vijay@gmail.com>
Cc: enh <enh@google.com>,
Venkat Venkatsubra <venkat.x.venkatsubra@oracle.com>,
netdev@vger.kernel.org
Subject: Re: listen(2) backlog changes in or around Linux 3.1?
Date: Fri, 26 Oct 2012 00:50:17 +0200 [thread overview]
Message-ID: <1351205417.6537.272.camel@edumazet-glaptop> (raw)
In-Reply-To: <CAGK4HS9N9b64pKobWE=9wM-ZqNL-uJiGoAWNkqu=F=-NgHM=0Q@mail.gmail.com>
On Mon, 2012-10-22 at 15:11 -0700, Vijay Subramanian wrote:
> >
> > All these facilities sound very complex and not really usable by clients
> > (ie users not willing to wait more than few seconds anyway)
> >
>
> Fair enough. We can drop this if it is not worth the trouble or if I
> have missed any other scenario.
>
Sorry my comment was not related to your patch, but existing logic.
It seems there is no value resending SYNACK, as we received the client
ACK.
Please send an official patch ?
next prev parent reply other threads:[~2012-10-25 22:50 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-10-12 23:40 listen(2) backlog changes in or around Linux 3.1? enh
2012-10-15 17:12 ` Venkat Venkatsubra
2012-10-15 17:26 ` enh
2012-10-15 21:30 ` Venkat Venkatsubra
2012-10-16 23:31 ` enh
2012-10-18 16:00 ` Venkat Venkatsubra
2012-10-18 16:53 ` Venkat Venkatsubra
2012-10-18 17:20 ` enh
2012-10-19 6:02 ` Vijay Subramanian
2012-10-19 6:50 ` Eric Dumazet
2012-10-19 8:06 ` Eric Dumazet
2012-10-19 9:14 ` Vijay Subramanian
2012-10-19 10:29 ` Eric Dumazet
2012-10-19 11:39 ` Eric Dumazet
2012-10-22 20:00 ` Vijay Subramanian
2012-10-22 20:08 ` Eric Dumazet
2012-10-22 22:11 ` Vijay Subramanian
2012-10-25 22:50 ` Eric Dumazet [this message]
2012-10-25 23:16 ` Vijay Subramanian
2012-10-18 16:54 ` 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=1351205417.6537.272.camel@edumazet-glaptop \
--to=eric.dumazet@gmail.com \
--cc=enh@google.com \
--cc=netdev@vger.kernel.org \
--cc=subramanian.vijay@gmail.com \
--cc=venkat.x.venkatsubra@oracle.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