All of lore.kernel.org
 help / color / mirror / Atom feed
From: Chris Friesen <chris.friesen@genband.com>
To: netdev@vger.kernel.org
Subject: ip fragments sent in reverse order?
Date: Thu, 26 May 2011 07:56:09 -0600	[thread overview]
Message-ID: <4DDE5BF9.6090508@genband.com> (raw)


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?

Thanks,
Chris


	
-- 
Chris Friesen
Software Developer
GENBAND
chris.friesen@genband.com
www.genband.com

             reply	other threads:[~2011-05-26 23:23 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-05-26 13:56 Chris Friesen [this message]
2011-05-27  0:20 ` ip fragments sent in reverse order? Changli Gao

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=4DDE5BF9.6090508@genband.com \
    --to=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 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.