From: "David S. Miller" <davem@davemloft.net>
To: herbert@gondor.apana.org.au
Cc: netdev@vger.kernel.org
Subject: Re: [TCP]: Account skb overhead in tcp_fragment
Date: Wed, 19 Apr 2006 21:31:15 -0700 (PDT) [thread overview]
Message-ID: <20060419.213115.74232309.davem@davemloft.net> (raw)
In-Reply-To: <20060420032602.GA21406@gondor.apana.org.au>
From: Herbert Xu <herbert@gondor.apana.org.au>
Date: Thu, 20 Apr 2006 13:26:02 +1000
> On Thu, Apr 20, 2006 at 11:01:11AM +1000, herbert wrote:
> > Hi Dave:
> >
> > Since sk_stream_alloc_pskb takes an extra argument that accounts for
> > paged data all we need to do to account sk_buff overhead correctly
> > is to use that instead of sk_stream_alloc_skb.
>
> Here is a better version that does not double-count the paged bits
> that get moved across.
>
> Signed-off-by: Herbert Xu <herbert@gondor.apana.org.au>
Looks good, I'll apply this.
prev parent reply other threads:[~2006-04-20 4:31 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-04-20 1:01 [TCP]: Account skb overhead in tcp_fragment Herbert Xu
2006-04-20 3:26 ` Herbert Xu
2006-04-20 4:31 ` David S. 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=20060419.213115.74232309.davem@davemloft.net \
--to=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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox