From: Eric Dumazet <eric.dumazet@gmail.com>
To: Tom Herbert <therbert@google.com>
Cc: davem@davemloft.net, netdev@vger.kernel.org
Subject: Re: [PATCH v2] xps-mp: Transmit Packet Steering for multiqueue
Date: Wed, 13 Oct 2010 07:48:13 +0200 [thread overview]
Message-ID: <1286948893.2703.88.camel@edumazet-laptop> (raw)
In-Reply-To: <alpine.DEB.1.00.1010121705500.15786@pokey.mtv.corp.google.com>
Le mardi 12 octobre 2010 à 17:20 -0700, Tom Herbert a écrit :
> +#ifdef CONFIG_RPS
> + struct kobject kobj;
> + struct netdev_queue *first;
> + atomic_t count;
> + struct xps_map *xps_maps;
> +#endif
Please put kobj at the end of this block, because its a big object (64
bytes)
+#ifdef CONFIG_RPS
> + struct xps_map *xps_maps;
> + struct netdev_queue *first;
> + atomic_t count;
> + struct kobject kobj;
> +#endif
>
This way, we only use one cache line to access hot path fields, instead
of two cache lines.
Tom, I believe you should split your patch in several parts, its really
too hard to review.
For example the netif_alloc_netdev_queues() stuff should be a patch on
its own, as this stuff was already discussed on netdev some days ago, so
that you could copy Ben and me on this one ;)
(Ie not allocating _tx in alloc_netdev_mq() but in register_netdevice())
Its also a good thing to give diffstat output :
include/linux/netdevice.h | 28 +++
include/linux/skbuff.h | 1
net/core/dev.c | 191 ++++++++++++++++------
net/core/net-sysfs.c | 305 +++++++++++++++++++++++++++++++++++-
net/core/net-sysfs.h | 3
net/ipv4/tcp_output.c | 4
6 files changed, 471 insertions(+), 61 deletions(-)
next prev parent reply other threads:[~2010-10-13 5:48 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-10-13 0:20 [PATCH v2] xps-mp: Transmit Packet Steering for multiqueue Tom Herbert
2010-10-13 5:48 ` Eric Dumazet [this message]
2010-10-13 15:41 ` Tom Herbert
2010-10-13 9:39 ` 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=1286948893.2703.88.camel@edumazet-laptop \
--to=eric.dumazet@gmail.com \
--cc=davem@davemloft.net \
--cc=netdev@vger.kernel.org \
--cc=therbert@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