From: Eric Dumazet <dada1@cosmosbay.com>
To: "Martin Schiller" <mschiller@tdt.de>
Cc: "'Lennert Buytenhek'" <buytenh@wantstofly.org>, netdev@vger.kernel.org
Subject: Re: Suppress / delay SYN-ACK
Date: Tue, 17 Oct 2006 14:54:19 +0200 [thread overview]
Message-ID: <200610171454.20193.dada1@cosmosbay.com> (raw)
In-Reply-To: <001501c6f1e4$5a23f020$1a04010a@V505CP>
On Tuesday 17 October 2006 14:04, Martin Schiller wrote:
> On Monday, October 16, 2006 9:02 AM, Lennert Buytenhek wrote:
> > I wrote something like this a couple of years ago:
> >
> > http://marc.theaimsgroup.com/?l=linux-netdev&m=103666165629419&w=2
> > http://marc.theaimsgroup.com/?l=linux-netdev&m=106089519611631&w=2
> >
> > There wasn't a whole lot of external interest, and my need for it
> > disappeared, so I never really finished it, and there's a couple of
> > unfixed bugs,
>
> Lennert's patch does nearly exactly the way how I tried to do it earlier by
> myself and after porting the patch to kernel 2.6.15.4 and 2.6.11.12, which
> I am currently using, it works great.
>
> The only change I've made is that I don't want to send the SYN-ACK only
> with the first write() on the socket, because in my application the
> requesting client is also the one who starts sending data. So I introduced
> an ioctl() which simply runs tcp_confirm() to send the SYN-ACK.
Well, did you solve Lennert problem if the final (third packet of three packet
TCP establishment handshake) packet is missing ?
It seems no timer will fire and tell you the socket is not usable...
Eric
next prev parent reply other threads:[~2006-10-17 12:54 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-10-12 8:08 Suppress / delay SYN-ACK Martin Schiller
2006-10-12 8:38 ` Eric Dumazet
2006-10-12 10:13 ` Martin Schiller
2006-10-12 10:31 ` Evgeniy Polyakov
2006-10-12 10:39 ` Eric Dumazet
2006-10-12 10:53 ` Evgeniy Polyakov
2006-10-12 10:36 ` Eric Dumazet
2006-10-12 16:13 ` Rick Jones
2006-10-12 21:58 ` Caitlin Bestler
2006-10-12 22:12 ` jamal
2006-10-12 22:54 ` Rick Jones
2006-10-13 0:57 ` Stephen Hemminger
2006-10-13 4:11 ` Eric Dumazet
2006-10-13 16:39 ` Rick Jones
2006-10-13 20:13 ` Eric Dumazet
2006-10-13 21:50 ` Rick Jones
2006-10-16 6:52 ` Martin Schiller
2006-10-13 5:41 ` Stephen J. Bevan
2006-10-13 6:28 ` Martin Schiller
2006-10-16 7:02 ` Lennert Buytenhek
2006-10-17 12:04 ` Martin Schiller
2006-10-17 12:54 ` Eric Dumazet [this message]
2006-10-18 6:23 ` Martin Schiller
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=200610171454.20193.dada1@cosmosbay.com \
--to=dada1@cosmosbay.com \
--cc=buytenh@wantstofly.org \
--cc=mschiller@tdt.de \
--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;
as well as URLs for NNTP newsgroup(s).