From: David Miller <davem@davemloft.net>
To: eric.dumazet@gmail.com
Cc: netdev@vger.kernel.org
Subject: Re: [PATCH v2 net-next] tcp: shrink tcp6_timewait_sock by one cache line
Date: Thu, 03 Oct 2013 17:43:57 -0400 (EDT) [thread overview]
Message-ID: <20131003.174357.89621984330679119.davem@davemloft.net> (raw)
In-Reply-To: <1380835645.19002.236.camel@edumazet-glaptop.roam.corp.google.com>
From: Eric Dumazet <eric.dumazet@gmail.com>
Date: Thu, 03 Oct 2013 14:27:25 -0700
> From: Eric Dumazet <edumazet@google.com>
>
> While working on tcp listener refactoring, I found that it
> would really make things easier if sock_common could include
> the IPv6 addresses needed in the lookups, instead of doing
> very complex games to get their values (depending on sock
> being SYN_RECV, ESTABLISHED, TIME_WAIT)
>
> For this to happen, I need to be sure that tcp6_timewait_sock
> and tcp_timewait_sock consume same number of cache lines.
>
> This is possible if we only use 32bits for tw_ttd, as we remove
> one 32bit hole in inet_timewait_sock
>
> inet_tw_time_stamp() is defined and used, even if its current
> implementation looks like tcp_time_stamp : We might need finer
> resolution for tcp_time_stamp in the future.
>
> Before patch : sizeof(struct tcp6_timewait_sock) = 0xc8
>
> After patch : sizeof(struct tcp6_timewait_sock) = 0xc0
>
> Signed-off-by: Eric Dumazet <edumazet@google.com>
> ---
> v2: add a inet_tw_time_stamp() helper, per David request.
Looks great, applied, thanks Eric.
next prev parent reply other threads:[~2013-10-03 21:44 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-10-02 11:00 [PATCH net-next] tcp: shrink tcp6_timewait_sock by one cache line Eric Dumazet
2013-10-02 12:08 ` David Laight
2013-10-02 14:57 ` Eric Dumazet
2013-10-03 19:31 ` David Miller
2013-10-03 19:47 ` Eric Dumazet
2013-10-03 20:02 ` David Miller
2013-10-03 21:22 ` Eric Dumazet
2013-10-03 21:27 ` [PATCH v2 " Eric Dumazet
2013-10-03 21:43 ` David Miller [this message]
2013-10-03 21:45 ` Eric Dumazet
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=20131003.174357.89621984330679119.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).