From mboxrd@z Thu Jan 1 00:00:00 1970 From: David Miller Subject: Re: [RFC PATCH] reuseport: compute the ehash only if needed Date: Thu, 14 Dec 2017 08:41:57 -0500 (EST) Message-ID: <20171214.084157.738105599035562640.davem@davemloft.net> References: <20171213.150855.2054919319089098824.davem@davemloft.net> <1513240186.2604.10.camel@redhat.com> Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit Cc: netdev@vger.kernel.org, kraig@google.com, edumazet@google.com To: pabeni@redhat.com Return-path: Received: from shards.monkeyblade.net ([184.105.139.130]:57524 "EHLO shards.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751029AbdLNNmB (ORCPT ); Thu, 14 Dec 2017 08:42:01 -0500 In-Reply-To: <1513240186.2604.10.camel@redhat.com> Sender: netdev-owner@vger.kernel.org List-ID: From: Paolo Abeni Date: Thu, 14 Dec 2017 09:29:46 +0100 > I was unable to measure any performance regression for the hash based > demultiplexing, and I think that the number of function calls is > unchanged in such scenario (with vanilla kernel we have ehash() and > reuseport_select_sock(), with the patched one __reuseport_get_info() > and ehash()). > > I agree you are right about the additional stack usage introduced by > this patch. > > Overall I see we need something better than this. Thanks for checking whether it's slower or not. I wonder if x86-64 is putting the argument parts on the stack anyways...