Linux Netfilter development
 help / color / mirror / Atom feed
From: Patrick McHardy <kaber@trash.net>
To: David Miller <davem@davemloft.net>
Cc: eric@inl.fr, jameshough@bemac.com, netfilter-devel@vger.kernel.org
Subject: Re: Large packets received from the queue
Date: Wed, 14 May 2008 12:09:55 +0200	[thread overview]
Message-ID: <482ABA73.5080109@trash.net> (raw)
In-Reply-To: <20080514.030605.175448517.davem@davemloft.net>

David Miller wrote:
> From: Patrick McHardy <kaber@trash.net>
> Date: Wed, 14 May 2008 10:53:52 +0200
> 
>> Actually we segment TSO frames before queuing because packet
>> modifications broke TSO.
> 
> We fixed that, or at least I thought we did :)


Yes, by segmenting :) At least thats what I thought, James
observation seems to contradict this. I'll run some tests
myself if I can find some time ...


  reply	other threads:[~2008-05-14 10:10 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-05-13 12:56 Large packets received from the queue james hough
2008-05-14  1:15 ` David Miller
2008-05-14  8:48   ` Eric Leblond
2008-05-14  8:53     ` Patrick McHardy
2008-05-14 10:06       ` David Miller
2008-05-14 10:09         ` Patrick McHardy [this message]
2008-05-14  9:08   ` james hough

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=482ABA73.5080109@trash.net \
    --to=kaber@trash.net \
    --cc=davem@davemloft.net \
    --cc=eric@inl.fr \
    --cc=jameshough@bemac.com \
    --cc=netfilter-devel@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox