From mboxrd@z Thu Jan  1 00:00:00 1970
Received: from out-176.mta1.migadu.com (out-176.mta1.migadu.com [95.215.58.176])
	(using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits))
	(No client certificate requested)
	by smtp.subspace.kernel.org (Postfix) with ESMTPS id 6D3E518A921
	for <linux-kernel@vger.kernel.org>; Tue, 14 Apr 2026 01:48:13 +0000 (UTC)
Authentication-Results: smtp.subspace.kernel.org; arc=none smtp.client-ip=95.215.58.176
ARC-Seal:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116;
	t=1776131294; cv=none; b=XQ/WUzgVYzRM2DIu0YVnXj1B98BqzvjtoESspR+pVncflemPfUyJquKXPiVeCHBzrkXwLYnBWzRIi6IgAzMfwd4eEoZiKZhyuiG9HLper1Yq0CN+/GeWW9YK/8CkNF3xSR7KFNPxoBJX/QPnAJ97nzLUKgzE59Ug9k5wSL9vW/s=
ARC-Message-Signature:i=1; a=rsa-sha256; d=subspace.kernel.org;
	s=arc-20240116; t=1776131294; c=relaxed/simple;
	bh=MtAwJlqd3nVO+JnPWiaK7BVIXHl14zYBqIuYYVvEhFk=;
	h=MIME-Version:Date:Content-Type:From:Message-ID:Subject:To:Cc:
	 In-Reply-To:References; b=Nezclw40+zg73M/9inrKKrxVoT/V/9wDtYVptx6mqpgJgTBUJiFRKm3P0ZS9mhExBzldf7eFobhcX4wP8CuP8j5FI7qq8FriDTLQuVRcwbnig/MNoaicxJmT7Mvm1qYn9zyN/O+bqwUF3nwB1naB9kxnb2b1nzs4n7pNlsRmUzk=
ARC-Authentication-Results:i=1; smtp.subspace.kernel.org; dmarc=pass (p=none dis=none) header.from=linux.dev; spf=pass smtp.mailfrom=linux.dev; dkim=pass (1024-bit key) header.d=linux.dev header.i=@linux.dev header.b=Ns+DQECg; arc=none smtp.client-ip=95.215.58.176
Authentication-Results: smtp.subspace.kernel.org; dmarc=pass (p=none dis=none) header.from=linux.dev
Authentication-Results: smtp.subspace.kernel.org; spf=pass smtp.mailfrom=linux.dev
Authentication-Results: smtp.subspace.kernel.org;
	dkim=pass (1024-bit key) header.d=linux.dev header.i=@linux.dev header.b="Ns+DQECg"
Precedence: bulk
X-Mailing-List: linux-kernel@vger.kernel.org
List-Id: <linux-kernel.vger.kernel.org>
List-Subscribe: <mailto:linux-kernel+subscribe@vger.kernel.org>
List-Unsubscribe: <mailto:linux-kernel+unsubscribe@vger.kernel.org>
MIME-Version: 1.0
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=linux.dev; s=key1;
	t=1776131281;
	h=from:from:reply-to:subject:subject:date:date:message-id:message-id:
	 to:to:cc:cc:mime-version:mime-version:content-type:content-type:
	 content-transfer-encoding:content-transfer-encoding:
	 in-reply-to:in-reply-to:references:references;
	bh=MtAwJlqd3nVO+JnPWiaK7BVIXHl14zYBqIuYYVvEhFk=;
	b=Ns+DQECgRX2Zm+kbhkaOW26GGREDdXaYEfaX0fUWJ/oC8eEtu6gtHmZl5FXuadz0h300zh
	mnHrBdylisavXW9uFMlPjoZHOYEcJINnUEGdV4AOPCVtmPrVtS/EfkqueEXdRo925fcPFP
	EuPUeN6L0TzAK4LNzgvFmvBGX6WojEQ=
Date: Tue, 14 Apr 2026 01:47:58 +0000
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: quoted-printable
X-Report-Abuse: Please report any abuse attempt to abuse@migadu.com and include these headers.
From: "Qingfang Deng" <qingfang.deng@linux.dev>
Message-ID: <5cae00a663a3830bacf172cd1cdee0c0c2640d4a@linux.dev>
TLS-Required: No
Subject: Re: [PATCH net-next] pppoe: optimize hash with word access
To: "Eric Dumazet" <edumazet@google.com>
Cc: "Andrew Lunn" <andrew+netdev@lunn.ch>, "David S. Miller"
 <davem@davemloft.net>, "Jakub Kicinski" <kuba@kernel.org>, "Paolo Abeni"
 <pabeni@redhat.com>, "Guillaume Nault" <gnault@redhat.com>, "Kees Cook"
 <kees@kernel.org>, "Eric Woudstra" <ericwouds@gmail.com>,
 netdev@vger.kernel.org, linux-kernel@vger.kernel.org
In-Reply-To: <CANn89iKmxWiCTt7nVk-DZ4R_KsYDYbPwQ5f7Hp5F8hWmr+zc=g@mail.gmail.com>
References: <20260413035212.56566-1-qingfang.deng@linux.dev>
 <CANn89iKmxWiCTt7nVk-DZ4R_KsYDYbPwQ5f7Hp5F8hWmr+zc=g@mail.gmail.com>
X-Migadu-Flow: FLOW_OUT

April 13, 2026 at 4:42 PM, Eric Dumazet wrote:

>=20
>=20On Sun, Apr 12, 2026 at 8:52 PM Qingfang Deng <qingfang.deng@linux.de=
v> wrote:
>=20
>=20net-next is closed.
>=20
>=20https://lore.kernel.org/netdev/20260412142250.131bf997@kernel.org/
>=20
>=20Also I would suggest using hash32(hash, PPPOE_HASH_BITS)

Thanks for the info, but I would like to keep the same algorithm.