From: Brice Goglin <Brice.Goglin@inria.fr>
To: Neil Horman <nhorman@tuxdriver.com>
Cc: Eric Dumazet <eric.dumazet@gmail.com>,
David Miller <davem@davemloft.net>,
netdev@vger.kernel.org
Subject: Re: [RFC] Idea about increasing efficency of skb allocation in network devices
Date: Wed, 29 Jul 2009 10:20:55 +0200 [thread overview]
Message-ID: <4A700667.5080108@inria.fr> (raw)
In-Reply-To: <20090727105554.GB15823@hmsreliant.think-freely.org>
Neil Horman wrote:
>>> Is there an easy way to get this NUMA node from the application socket
>>> descriptor?
>>>
>> Thats not easy, this information can change for every packet (think of
>> bonding setups, whith aggregation of devices on different NUMA nodes)
>>
>> We could add a getsockopt() call to peek this information from the next
>> data to be read from socket (returns node id where skb data is sitting,
>> hoping that NIC driver hadnt copybreak it (ie : allocate a small skb and
>> copy the device provided data on it before feeding packet to network stack))
>>
>>
> Would a proc or debugfs interface perhaps be helpful here? Something that
> perhaps showed a statistical distribution of how many packets were received by
> each process on each irq (operating under the assumption that each rx queue has
> its own msi irq, giving us an easy identifier).
>
It could be intereting. But unprivileged user processes cannot read
/proc/irq/*/smp_affinity, so they would not be able to translate your
procfs information into a binding hint.
Brice
next prev parent reply other threads:[~2009-07-29 8:20 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-07-27 0:36 [RFC] Idea about increasing efficency of skb allocation in network devices Neil Horman
2009-07-27 1:02 ` David Miller
2009-07-27 7:10 ` Brice Goglin
2009-07-27 7:58 ` Eric Dumazet
2009-07-27 8:27 ` Brice Goglin
2009-07-27 10:55 ` Neil Horman
2009-07-29 8:20 ` Brice Goglin [this message]
2009-07-29 10:47 ` Neil Horman
2009-07-27 10:52 ` Neil Horman
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=4A700667.5080108@inria.fr \
--to=brice.goglin@inria.fr \
--cc=davem@davemloft.net \
--cc=eric.dumazet@gmail.com \
--cc=netdev@vger.kernel.org \
--cc=nhorman@tuxdriver.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;
as well as URLs for NNTP newsgroup(s).