From: David Miller <davem@davemloft.net>
To: rauhersu@gmail.com
Cc: ilpo.jarvinen@helsinki.fi, netdev@vger.kernel.org
Subject: Re: high rate injection and fragmentation
Date: Mon, 09 Feb 2009 15:10:58 -0800 (PST) [thread overview]
Message-ID: <20090209.151058.193026368.davem@davemloft.net> (raw)
In-Reply-To: <3f847c820902090918j4da4b94o3eee35415f088afb@mail.gmail.com>
From: Raúl Hernández <rauhersu@gmail.com>
Date: Mon, 9 Feb 2009 18:18:50 +0100
> Hi Ilpo,
>
> Thanks for your answer, I did not know about that feature. Looking at
> my settings:
>
> # ethtool -k eth2
> ...
> tcp segmentation offload: on
>
> I think ethereal hooks up before reaching the TCP offload which is
> handled by the NIC.
No, the packets will be large as created by the TCP stack,
and then the NIC hardware splits them up as it transmits
them onto the wire.
prev parent reply other threads:[~2009-02-09 23:11 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-02-09 15:20 high rate injection and fragmentation Raúl Hernández
2009-02-09 16:09 ` Ilpo Järvinen
2009-02-09 17:18 ` Raúl Hernández
2009-02-09 23:10 ` David Miller [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=20090209.151058.193026368.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=ilpo.jarvinen@helsinki.fi \
--cc=netdev@vger.kernel.org \
--cc=rauhersu@gmail.com \
/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).