From: David Miller <davem@davemloft.net>
To: brakmo@fb.com
Cc: netdev@vger.kernel.org, kernel-team@fb.com, ncardwell@google.com,
eric.dumazet@gmail.com, ycheng@google.com
Subject: Re: [PATCH net-next] tcp: refactor struct tcp_skb_cb
Date: Mon, 09 May 2016 00:06:24 -0400 (EDT) [thread overview]
Message-ID: <20160509.000624.2258641144075621164.davem@davemloft.net> (raw)
In-Reply-To: <1462592135-1905403-1-git-send-email-brakmo@fb.com>
From: Lawrence Brakmo <brakmo@fb.com>
Date: Fri, 6 May 2016 20:35:35 -0700
> Refactor tcp_skb_cb to create two overlaping areas to store
> state for incoming or outgoing skbs based on comments by
> Neal Cardwell to tcp_nv patch:
>
> AFAICT this patch would not require an increase in the size of
> sk_buff cb[] if it were to take advantage of the fact that the
> tcp_skb_cb header.h4 and header.h6 fields are only used in the packet
> reception code path, and this in_flight field is only used on the
> transmit side.
>
> Signed-off-by: Lawrence Brakmo <brakmo@fb.com>
> Acked-by: Yuchung Cheng <ycheng@google.com>
Applied.
prev parent reply other threads:[~2016-05-09 4:06 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-05-07 3:35 [PATCH net-next] tcp: refactor struct tcp_skb_cb Lawrence Brakmo
2016-05-09 4:06 ` 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=20160509.000624.2258641144075621164.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=brakmo@fb.com \
--cc=eric.dumazet@gmail.com \
--cc=kernel-team@fb.com \
--cc=ncardwell@google.com \
--cc=netdev@vger.kernel.org \
--cc=ycheng@google.com \
/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