From: David Miller <davem@davemloft.net>
To: eric.dumazet@gmail.com
Cc: netdev@vger.kernel.org
Subject: Re: [PATCH net-next] tcp: tcp_make_synack() minor changes
Date: Wed, 26 Mar 2014 15:12:09 -0400 (EDT) [thread overview]
Message-ID: <20140326.151209.653481434539419400.davem@davemloft.net> (raw)
In-Reply-To: <1395860927.12610.226.camel@edumazet-glaptop2.roam.corp.google.com>
From: Eric Dumazet <eric.dumazet@gmail.com>
Date: Wed, 26 Mar 2014 12:08:47 -0700
> On Wed, 2014-03-26 at 14:25 -0400, David Miller wrote:
>> Do you know where this "+ 15" comes from? :-)
>>
>> It is a kind of Linux networking trivia question.
>
> My random guess would be that it is related to a copy/paste
> thing, as some tx paths used to allocate skb with a very precise byte
> count, and they used HH_DATA_ALIGN().
Yes, this is exactly it.
next prev parent reply other threads:[~2014-03-26 19:12 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-03-26 16:57 [PATCH net-next] tcp: tcp_make_synack() minor changes Eric Dumazet
2014-03-26 18:25 ` David Miller
2014-03-26 18:52 ` Joe Perches
2014-03-26 19:11 ` David Miller
2014-03-26 19:08 ` Eric Dumazet
2014-03-26 19:12 ` David Miller [this message]
2014-03-27 19:10 ` David Miller
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=20140326.151209.653481434539419400.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=eric.dumazet@gmail.com \
--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;
as well as URLs for NNTP newsgroup(s).