From: David Miller <davem@davemloft.net>
To: dada1@cosmosbay.com
Cc: dm@chelsio.com, netdev@vger.kernel.org, w@1wt.eu
Subject: Re: [PATCH] Fix tcp splice length
Date: Mon, 26 Jan 2009 22:14:52 -0800 (PST) [thread overview]
Message-ID: <20090126.221452.157337515.davem@davemloft.net> (raw)
In-Reply-To: <497EA55A.2050905@cosmosbay.com>
From: Eric Dumazet <dada1@cosmosbay.com>
Date: Tue, 27 Jan 2009 07:10:34 +0100
> Nice spot Dimitris !
>
> Acked-by: Eric Dumazet <dada1@cosmosbay.com>
Ok, I'll apply this.
> This fixes a bug present in previous linux versions (before commit
> 33966dd0e2f68f26943cd9ee93ec6abbc6547a8e tcp: splice as many packets
> as possible at once)
>
> It should be backported as well, changing tss->len by min(tss->len, len) ?
Indeed, I'll queue this up for -stable to remind myself about
this.
Thanks Eric.
prev parent reply other threads:[~2009-01-27 6:14 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-01-27 5:12 [PATCH] Fix tcp splice length Dimitris Michailidis
2009-01-27 5:29 ` David Miller
2009-01-27 6:10 ` Eric Dumazet
2009-01-27 6:14 ` 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=20090126.221452.157337515.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=dada1@cosmosbay.com \
--cc=dm@chelsio.com \
--cc=netdev@vger.kernel.org \
--cc=w@1wt.eu \
/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