From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from smtp.kernel.org (aws-us-west-2-korg-mail-1.web.codeaurora.org [10.30.226.201]) (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 6637B17CB; Tue, 17 Oct 2023 01:27:27 +0000 (UTC) Authentication-Results: smtp.subspace.kernel.org; dkim=pass (2048-bit key) header.d=kernel.org header.i=@kernel.org header.b="HogMLJfe" Received: by smtp.kernel.org (Postfix) with ESMTPSA id 9245CC433C7; Tue, 17 Oct 2023 01:27:26 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=kernel.org; s=k20201202; t=1697506047; bh=s+jRDW+2r/hfeMcX43wig5Zoi67P+MBXYRuEZHkr50I=; h=Date:From:To:Cc:Subject:In-Reply-To:References:From; b=HogMLJfecZN17MTZr096mjcZ2IDGruz/FY7v83Gb7/ZDvPTIL+WdGM2mSjH7TIQeV lkrcwJlrreWA553L9DrttaF+M7rIPrW9D9ajMAl90ghSw45tWbn0TqygnVdba71bsJ BvKjL+VYXfZH4UypliqZOJuU3w2NObAhUxlv8cKc2lrEzWW7ASoP3AVNUGpU8o8sPF UnRi6125QGaEN9A5JIvhzI7DWQnCDQH6LUuKqXlkSo5Jy3x640fO1wpZfyv1n/b4q+ D0RssdFIOutKYuMPzDFSpjElHznI23230BDvGHOLDdKzk7TVCqfAwWBq2gAt0PN03C fcg5fAqQT0iKw== Date: Mon, 16 Oct 2023 18:27:25 -0700 From: Jakub Kicinski To: Yunsheng Lin Cc: , , , , Alexei Starovoitov , Daniel Borkmann , Jesper Dangaard Brouer , John Fastabend , Matthias Brugger , AngeloGioacchino Del Regno , , , Subject: Re: [PATCH net-next v11 0/6] introduce page_pool_alloc() related API Message-ID: <20231016182725.6aa5544f@kernel.org> In-Reply-To: <20231013064827.61135-1-linyunsheng@huawei.com> References: <20231013064827.61135-1-linyunsheng@huawei.com> Precedence: bulk X-Mailing-List: netdev@vger.kernel.org List-Id: List-Subscribe: List-Unsubscribe: MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit On Fri, 13 Oct 2023 14:48:20 +0800 Yunsheng Lin wrote: > v5 RFC: Add a new page_pool_cache_alloc() API, and other minor > change as discussed in v4. As there seems to be three > comsumers that might be made use of the new API, so > repost it as RFC and CC the relevant authors to see > if the new API fits their need. I have looked thru the v4 discussion (admittedly it was pretty huge). I can't find where the "cache" API was suggested. And I can't figure out now what the "cache" in the name is referring to. Looks like these are just convenience wrappers which return VA instead of struct page..