From: Changli Gao <xiaosuo@gmail.com>
To: Chris Friesen <chris.friesen@genband.com>
Cc: netdev@vger.kernel.org
Subject: Re: ip fragments sent in reverse order?
Date: Fri, 27 May 2011 08:20:02 +0800 [thread overview]
Message-ID: <BANLkTimTLoJkmD77NGcdgRaayT+Uj06YpA@mail.gmail.com> (raw)
In-Reply-To: <4DDE5BF9.6090508@genband.com>
On Thu, May 26, 2011 at 9:56 PM, Chris Friesen
<chris.friesen@genband.com> wrote:
>
> I read that Linux intentionally sends IP fragments in reverse order to allow
> for some optimization on the receive side. I'm trying to find this code,
> but what I see in ip_fragment() seems to be creating/sending the fragments
> in order. Has this changed over the years?
>
Yes. Now the fragments are sent in order.
--
Regards,
Changli Gao(xiaosuo@gmail.com)
prev parent reply other threads:[~2011-05-27 0:20 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-05-26 13:56 ip fragments sent in reverse order? Chris Friesen
2011-05-27 0:20 ` Changli Gao [this message]
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=BANLkTimTLoJkmD77NGcdgRaayT+Uj06YpA@mail.gmail.com \
--to=xiaosuo@gmail.com \
--cc=chris.friesen@genband.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;
as well as URLs for NNTP newsgroup(s).