From: Andrew Gallatin <gallatin@myri.com>
To: David Miller <davem@davemloft.net>
Cc: herbert@gondor.apana.org.au, netdev@vger.kernel.org, brice@myri.com
Subject: Re: LRO restructuring?
Date: Tue, 12 Aug 2008 07:50:58 -0400 [thread overview]
Message-ID: <48A17922.4050103@myri.com> (raw)
In-Reply-To: <20080811.140351.54834488.davem@davemloft.net>
David Miller wrote:
> From: Andrew Gallatin <gallatin@myri.com>
> Date: Mon, 11 Aug 2008 09:30:33 -0400
>
>> Last, have you considered simply allowing "inexact" forwarding, where
>> the ingress NIC is doing LRO and the egress nic is doing TSO? You
>> loose exact framing information (eg, what you emit might not be framed
>> exactly as you receive it), but you can still do filtering, and the
>> host overhead is very low.
>
> Intermediate nodes are not supposed to change the transport layer
> checksum if at all possible, especially on routers.
Indeed. Nor should they change lengths, or anything else.
Everything about this "inexact" forwarding is illegal as
hell. However, you have to admit that it is an interesting hack :)
Drew
next prev parent reply other threads:[~2008-08-12 11:51 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-08-11 13:30 LRO restructuring? Andrew Gallatin
2008-08-11 21:03 ` David Miller
2008-08-12 11:50 ` Andrew Gallatin [this message]
2008-08-13 2:14 ` Herbert Xu
2008-08-12 0:50 ` Herbert Xu
2008-08-12 0:54 ` David Miller
2008-08-12 1:00 ` Herbert Xu
2008-08-12 1:30 ` Rick Jones
2008-08-12 1:39 ` David Miller
2008-08-12 1:53 ` Herbert Xu
2009-02-18 19:25 ` James Huang
2009-02-18 19:42 ` Ben Hutchings
2009-02-18 19:46 ` Stephen Hemminger
2009-02-19 13:53 ` Herbert Xu
2009-02-19 22:20 ` James Huang
[not found] ` <f0ed9b110902191417k2917d856q9098b304eeb7435b@mail.gmail.com>
2009-02-20 0:37 ` Herbert Xu
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=48A17922.4050103@myri.com \
--to=gallatin@myri.com \
--cc=brice@myri.com \
--cc=davem@davemloft.net \
--cc=herbert@gondor.apana.org.au \
--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.