From: Eliezer Tamir <eliezer.tamir@linux.intel.com>
To: Shawn Bohrer <sbohrer@rgmadvisors.com>
Cc: davem@davemloft.net, netdev@vger.kernel.org,
Amir Vadai <amirv@mellanox.com>,
tomk@rgmadvisors.com
Subject: Re: [PATCH net-next] net: Add low-latency/polling support for UDP multicast
Date: Tue, 06 Aug 2013 10:13:07 +0300 [thread overview]
Message-ID: <5200A203.2090306@linux.intel.com> (raw)
In-Reply-To: <1375741001-20553-1-git-send-email-sbohrer@rgmadvisors.com>
On 06/08/2013 01:16, Shawn Bohrer wrote:
> Set the napi id for each socket in the multicast path to enable
> low-latency/polling support.
>
> Signed-off-by: Shawn Bohrer <sbohrer@rgmadvisors.com>
> ---
> net/ipv4/udp.c | 1 +
> 1 files changed, 1 insertions(+), 0 deletions(-)
>
> diff --git a/net/ipv4/udp.c b/net/ipv4/udp.c
> index 766e6ba..0d0da17 100644
> --- a/net/ipv4/udp.c
> +++ b/net/ipv4/udp.c
> @@ -1596,6 +1596,7 @@ static int __udp4_lib_mcast_deliver(struct net *net, struct sk_buff *skb,
> dif = skb->dev->ifindex;
> sk = udp_v4_mcast_next(net, sk, uh->dest, daddr, uh->source, saddr, dif);
> while (sk) {
> + sk_mark_napi_id(sk, skb);
> stack[count++] = sk;
> sk = udp_v4_mcast_next(net, sk_nulls_next(sk), uh->dest,
> daddr, uh->source, saddr, dif);
>
Looks OK.
To be complete, you want to do the same for __udp6_lib_mcast_deliver().
-Eliezer
next prev parent reply other threads:[~2013-08-06 7:13 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-08-05 21:22 low latency/busy poll feedback and bugs Shawn Bohrer
2013-08-05 22:16 ` [PATCH net-next] net: Add low-latency/polling support for UDP multicast Shawn Bohrer
2013-08-06 7:13 ` Eliezer Tamir [this message]
2013-08-06 19:51 ` [PATCH v2 " Shawn Bohrer
2013-08-07 20:22 ` Eric Dumazet
2013-08-08 8:46 ` Eliezer Tamir
2013-08-08 23:55 ` Eric Dumazet
2013-08-11 7:59 ` Eliezer Tamir
2013-08-06 7:41 ` low latency/busy poll feedback and bugs Eliezer Tamir
2013-08-06 18:08 ` Shawn Bohrer
2013-08-06 18:25 ` Eliezer Tamir
2013-08-07 20:05 ` Ben Hutchings
2013-08-07 20:23 ` Eric Dumazet
2013-08-07 23:41 ` David Miller
2013-08-06 20:39 ` Or Gerlitz
2013-08-06 21:02 ` Eric Dumazet
2013-08-06 12:15 ` Amir Vadai
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=5200A203.2090306@linux.intel.com \
--to=eliezer.tamir@linux.intel.com \
--cc=amirv@mellanox.com \
--cc=davem@davemloft.net \
--cc=netdev@vger.kernel.org \
--cc=sbohrer@rgmadvisors.com \
--cc=tomk@rgmadvisors.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).