From: Eric Dumazet <eric.dumazet@gmail.com>
To: Brian Haley <brian.haley@hp.com>
Cc: David Miller <davem@davemloft.net>, netdev <netdev@vger.kernel.org>
Subject: Re: [PATCH net-next-2.6] net: optimize INET input path further
Date: Wed, 01 Dec 2010 18:42:38 +0100 [thread overview]
Message-ID: <1291225358.2856.1035.camel@edumazet-laptop> (raw)
In-Reply-To: <4CF687F3.7030107@hp.com>
Le mercredi 01 décembre 2010 à 12:37 -0500, Brian Haley a écrit :
> On 12/01/2010 12:04 AM, Eric Dumazet wrote:
> > struct sock_common {
> > - /*
> > - * first fields are not copied in sock_copy()
> > + /* skc_daddr and skc_rcv_saddr must be grouped :
> > + * cf INET_MATCH() and INET_TW_MATCH()
> > */
> > - union {
> > - struct hlist_node skc_node;
> > - struct hlist_nulls_node skc_nulls_node;
> > - };
> > - atomic_t skc_refcnt;
> > - int skc_tx_queue_mapping;
> > + __be32 skc_daddr;
> > + __be32 skc_rcv_saddr;
> >
> > union {
> > unsigned int skc_hash;
>
> Putting IPv4 addresses in sock_common doesn't make it so common anymore :)
>
> Is it possible to make this a union so other address families like IPv6
> can benefit from this as well, or will that blow the whole cache line
> effect you were trying to achieve?
This might be OK, depending on cache line size and/or arch.
On x86_32 for example, that might even be a good thing, because refcnt
might still be in the first 64bytes of socket.
By the way, ipv6 sock includes inet, so includes ipv4 addresses too, I
only moved them in the 'whole structure'
next prev parent reply other threads:[~2010-12-01 17:42 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-12-01 5:04 [PATCH net-next-2.6] net: optimize INET input path further Eric Dumazet
2010-12-01 17:37 ` Brian Haley
2010-12-01 17:42 ` Eric Dumazet [this message]
2010-12-01 18:00 ` Brian Haley
2010-12-03 17:11 ` David Miller
2010-12-10 4:07 ` 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=1291225358.2856.1035.camel@edumazet-laptop \
--to=eric.dumazet@gmail.com \
--cc=brian.haley@hp.com \
--cc=davem@davemloft.net \
--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