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: Thu, 27 Mar 2014 15:10:34 -0400 (EDT) [thread overview]
Message-ID: <20140327.151034.1733885339640746031.davem@davemloft.net> (raw)
In-Reply-To: <1395853039.12610.217.camel@edumazet-glaptop2.roam.corp.google.com>
From: Eric Dumazet <eric.dumazet@gmail.com>
Date: Wed, 26 Mar 2014 09:57:19 -0700
> From: Eric Dumazet <edumazet@google.com>
>
> There is no need to allocate 15 bytes in excess for a SYNACK packet,
> as it contains no data, only headers.
>
> SYNACK are always generated in softirq context, and contain a single
> segment, we can use TCP_INC_STATS_BH()
>
> Signed-off-by: Eric Dumazet <edumazet@google.com>
Applied, thanks.
prev parent reply other threads:[~2014-03-27 19:10 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
2014-03-27 19: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=20140327.151034.1733885339640746031.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).