[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <20170920.202022.2073272587145961156.davem@davemloft.net>
Date: Wed, 20 Sep 2017 20:20:22 -0700 (PDT)
From: David Miller <davem@...emloft.net>
To: pabeni@...hat.com
Cc: netdev@...r.kernel.org, pablo@...filter.org, fw@...len.de,
edumazet@...gle.com, hannes@...essinduktion.org
Subject: Re: [PATCH net-next 0/5] net: introduce noref sk
From: Paolo Abeni <pabeni@...hat.com>
Date: Wed, 20 Sep 2017 18:54:00 +0200
> This series introduce the infrastructure to store inside the skb a socket
> pointer without carrying a refcount to the socket.
>
> Such infrastructure is then used in the network receive path - and
> specifically the early demux operation.
>
> This allows the UDP early demux to perform a full lookup for UDP sockets,
> with many benefits:
>
> - the UDP early demux code is now much simpler
> - the early demux does not hit any performance penalties in case of UDP hash
> table collision - previously the early demux performed a partial, unsuccesful,
> lookup
> - early demux is now operational also for unconnected sockets.
>
> This infrastrcture will be used in follow-up series to allow dst caching for
> unconnected UDP sockets, and than to extend the same features to TCP listening
> sockets.
Like Eric, I find this series (while exciting) quite scary :-)
You really have to post some kind of performance numbers in your
header posting in order to justify something with these ramifications
and scale.
Thank you.
Powered by blists - more mailing lists