netdev - ip fragments sent in reverse order?

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [thread-next>] [day] [month] [year] [list]

Date:	Thu, 26 May 2011 07:56:09 -0600
From:	Chris Friesen <chris.friesen@...band.com>
To:	netdev@...r.kernel.org
Subject: ip fragments sent in reverse order?

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@...band.com
www.genband.com
--
To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html