From: Vlad Yasevich <vyasevich@gmail.com>
To: Eric Dumazet <eric.dumazet@gmail.com>
Cc: "netdev@vger.kernel.org" <netdev@vger.kernel.org>
Subject: Re: udp v6 early demux?
Date: Tue, 10 Feb 2015 21:53:48 -0500 [thread overview]
Message-ID: <54DAC43C.2090101@gmail.com> (raw)
In-Reply-To: <1423589555.28434.36.camel@edumazet-glaptop2.roam.corp.google.com>
On 02/10/2015 12:32 PM, Eric Dumazet wrote:
> On Tue, 2015-02-10 at 12:14 -0500, Vlad Yasevich wrote:
>> Hi
>>
>> While testing udpv6 lockless path, I noticed that there is no
>> support for udpv6 early demux? Is there a technical reason why,
>> or was this just something that got forgotten (kind of like
>> lockeless sendmsg)?
>
> If you have a use case for connected UDP ipv6 flows with performance
> issues, then you might add early demux I guess.
>
> IPv4 udp early demux has been a bit of a hack actually,
> as Shawn main usage was multicast AFAIK
>
> 63c6f81cdde5 udp: ipv4: do not waste time in __udp4_lib_mcast_demux_lookup
> 610438b74496 udp: ipv4: fix potential use after free in udp_v4_early_demux()
> f69b923a758f udp: fix a typo in __udp4_lib_mcast_demux_lookup
> 421b3885bf6d udp: ipv4: Add udp early demux
>
>
I was more wondering if we can avoid the route the lookup. It may not always be
a connected a case. If you have multiple senders and a single receiver on the
same subnet, avoiding the route lookup with early demux might help.
-vlad
next prev parent reply other threads:[~2015-02-11 2:53 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-02-10 17:14 udp v6 early demux? Vlad Yasevich
2015-02-10 17:32 ` Eric Dumazet
2015-02-11 2:53 ` Vlad Yasevich [this message]
2015-02-11 4:57 ` 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=54DAC43C.2090101@gmail.com \
--to=vyasevich@gmail.com \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.