From: Joris van Rantwijk <joris@jorisvr.nl>
To: "Ilpo Järvinen" <ilpo.jarvinen@helsinki.fi>
Cc: Netdev <netdev@vger.kernel.org>
Subject: Re: Question about LRO/GRO and TCP acknowledgements
Date: Tue, 14 Jun 2011 21:37:18 +0200 [thread overview]
Message-ID: <20110614213718.67022768@konijn> (raw)
In-Reply-To: <alpine.DEB.2.00.1106141302110.17529@wel-95.cs.helsinki.fi>
On 2011-06-14, "Ilpo Järvinen" <ilpo.jarvinen@helsinki.fi> wrote:
> BTW, it wouldn't be impossible to create all those "missing" ACKs on
> the TCP layer relatively cheaply when receiving the GRO'ed super
> segment. I'm certainly not opposed you coming up such patch which
> does all that minimal work needed on TCP layer but I think it
> requires also some TSO/GSO related problem solving because TSO/GSO as
> is won't let you create such super ACKs we'd want to send out on that
> single go.
Your super-ACK idea is similar to the solution presented in this paper:
http://www.usenix.org/event/usenix08/tech/full_papers/menon/menon_html/
Actually, I started looking at the GRO code after reading that
paper, hoping to find that Linux has a better way to deal with ACKs.
The super ACK doesn't look easy. It must contain all different ack_seq
values to avoid tripping duplicate ACK detection. Ideally, the ack_seq
values would match real seq values from the received segments.
I don't currently have a setup where I could test these kinds of
changes, so this doesn't seem like a job for me. At least not right now.
Thanks, Joris.
next prev parent reply other threads:[~2011-06-14 19:37 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-06-11 19:59 Question about LRO/GRO and TCP acknowledgements Joris van Rantwijk
2011-06-12 3:43 ` Ben Hutchings
2011-06-12 7:51 ` Joris van Rantwijk
2011-06-12 9:07 ` Eric Dumazet
2011-06-12 9:30 ` Joris van Rantwijk
2011-06-12 10:48 ` Eric Dumazet
2011-06-12 11:24 ` Joris van Rantwijk
2011-06-12 12:01 ` Alexander Zimmermann
2011-06-12 14:57 ` Eric Dumazet
2011-06-12 19:37 ` Joris van Rantwijk
2011-06-14 10:53 ` Ilpo Järvinen
2011-06-14 19:37 ` Joris van Rantwijk [this message]
2011-06-13 17:55 ` Rick Jones
2011-06-13 17:34 ` Rick Jones
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=20110614213718.67022768@konijn \
--to=joris@jorisvr.nl \
--cc=ilpo.jarvinen@helsinki.fi \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.