From: Jerry Van Baren <gvb.uboot@gmail.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH/RFC] net: defragment IP packets
Date: Sat, 25 Jul 2009 22:02:48 -0400 [thread overview]
Message-ID: <4A6BB948.1000900@gmail.com> (raw)
In-Reply-To: <200907251809.07327.rgetz@blackfin.uclinux.org>
Robin Getz wrote:
> On Fri 24 Jul 2009 04:04, Alessandro Rubini pondered:
>> This patch add a quick and dirty defrag step in IP reception. This
>> allows to increase the TFTP block size and get more performance in
>> slow links (but at that point it should be made configurable).
>>
>> The overhead is negligible, verified with an ARM9 CPU and 10MB data
>> file, changing the server MTU from 1500 to 800 and then 550. However,
>> on a LAN connection, I didn't see advantes with using a 4k block
>> size with default MTU.
[snip]
> I needed to modify your patch a little bit to get it working on my platform.
>
> If Ben/Wolfgang are interested in taking this - I'll fix up my mods, and send
> it back.
>
> -Robin
FWIIW, RFC815 describes a reassembly algorithm that handles out-of-order
reassembly directly in the receive buffer by keeping the "holes"
bookkeeping data in the holes themselves.
<http://www.faqs.org/rfcs/rfc815.html>
Best regards,
gvb
next prev parent reply other threads:[~2009-07-26 2:02 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-07-24 8:04 [U-Boot] [PATCH/RFC] net: defragment IP packets Alessandro Rubini
2009-07-25 22:09 ` Robin Getz
2009-07-26 2:02 ` Jerry Van Baren [this message]
2009-07-26 4:44 ` Robin Getz
2009-07-26 20:23 ` Alessandro Rubini
2009-07-27 0:19 ` Robin Getz
2009-07-27 5:08 ` Ben Warren
2009-07-27 11:46 ` Robin Getz
2009-07-27 0:59 ` Robin Getz
2009-07-27 12:13 ` Alessandro Rubini
2009-07-27 12:52 ` Robin Getz
2009-07-27 12:41 ` Wolfgang Denk
2009-07-27 12:50 ` Robin Getz
2009-07-27 11:41 ` Robin Getz
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=4A6BB948.1000900@gmail.com \
--to=gvb.uboot@gmail.com \
--cc=u-boot@lists.denx.de \
/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.