From: Simon Horman <simon.horman@netronome.com>
To: Eric Dumazet <eric.dumazet@gmail.com>
Cc: Subash Abhinov Kasiviswanathan <subashab@codeaurora.org>,
netdev@vger.kernel.org, netdev-owner@vger.kernel.org
Subject: Re: [PATCH net-next] net: ipv6: Add early demux handler for UDP unicast
Date: Tue, 18 Apr 2017 17:09:04 +0900 [thread overview]
Message-ID: <20170418080902.GA25804@vergenet.net> (raw)
In-Reply-To: <1489000921.28631.18.camel@edumazet-glaptop3.roam.corp.google.com>
On Wed, Mar 08, 2017 at 11:22:01AM -0800, Eric Dumazet wrote:
> On Wed, 2017-03-08 at 12:11 -0700, Subash Abhinov Kasiviswanathan wrote:
> > On 2017-03-08 11:40, Eric Dumazet wrote:
> > > Well, this 'optimization' actually hurts when UDP sockets are not
> > > connected, since this adds an extra cache line miss per incoming
> > > packet.
> > >
> > > (DNS servers for example)
> >
> > Hi Eric
> >
> > Thanks for your comments. Would it be preferable to disable early demux
> > for the
> > servers with large unconnected workloads in that case?
>
> Well, many servers handle both TCP and UDP.
>
> For TCP, there is no question about early demux, this is definitely a
> win.
>
> We probably should have one sysctl to enable TCP early demux, one for
> UDP early demux.
If early demux is a clear win for TCP then I wonder if it is
unnecessary and by some leap also undesirable to have a configuration
knob for that case.
next prev parent reply other threads:[~2017-04-18 8:09 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-08 18:24 [PATCH net-next] net: ipv6: Add early demux handler for UDP unicast Subash Abhinov Kasiviswanathan
2017-03-08 18:40 ` Eric Dumazet
2017-03-08 19:11 ` Subash Abhinov Kasiviswanathan
2017-03-08 19:22 ` Eric Dumazet
2017-04-18 8:09 ` Simon Horman [this message]
2017-04-18 15:16 ` David Miller
2017-04-18 18:09 ` Hannes Frederic Sowa
2017-04-18 23:06 ` Simon 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=20170418080902.GA25804@vergenet.net \
--to=simon.horman@netronome.com \
--cc=eric.dumazet@gmail.com \
--cc=netdev-owner@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=subashab@codeaurora.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.