From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org Received: from bombadil.infradead.org (bombadil.infradead.org [198.137.202.133]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by smtp.lore.kernel.org (Postfix) with ESMTPS id E9F9FC25B67 for ; Tue, 24 Oct 2023 02:25:12 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=lists.infradead.org; s=bombadil.20210309; h=Sender: Content-Transfer-Encoding:Content-Type:List-Subscribe:List-Help:List-Post: List-Archive:List-Unsubscribe:List-Id:MIME-Version:References:In-Reply-To: Message-ID:Subject:Cc:To:From:Date:Reply-To:Content-ID:Content-Description: Resent-Date:Resent-From:Resent-Sender:Resent-To:Resent-Cc:Resent-Message-ID: List-Owner; bh=PDGNm7QbS4v2hAtrPvjxMsB2Fqkz48A3eyaTw+It41A=; b=Y3hTrwwlZPmspu rtUTg+RZksHVKOQHhua6kezplL5uJjbm7iWqcXcYRF3L6bOawikWLUI5eJMBMhVDnn3c/cHsI3Em4 3h1dYH3G47Uvzriq9yw6E1vhpkfN5sN4uzuUibO6DrjfomtAUu4IG5TXmCqfNUSip2fawSGr9iPZV kqlwIedAJi7iXDmx4rbTE1n89swmvjzLyIPSC9aJNIHpri8VG/+iUxRlwk8eRwAzehj6KW/Isx5tb ++Q27aqLFGAELLa6PxBNwbsN1PFTB73MuuchQgcLkvmGUQWlK7fAw/Xkz70zrGJjSY9E8rAr55dx0 NggmDoNEc1hFGxDRIkhQ==; Received: from localhost ([::1] helo=bombadil.infradead.org) by bombadil.infradead.org with esmtp (Exim 4.96 #2 (Red Hat Linux)) id 1qv760-008eJz-1J; Tue, 24 Oct 2023 02:24:40 +0000 Received: from dfw.source.kernel.org ([139.178.84.217]) by bombadil.infradead.org with esmtps (Exim 4.96 #2 (Red Hat Linux)) id 1qv75x-008eJZ-32; Tue, 24 Oct 2023 02:24:39 +0000 Received: from smtp.kernel.org (transwarp.subspace.kernel.org [100.75.92.58]) by dfw.source.kernel.org (Postfix) with ESMTP id C28BC6289A; Tue, 24 Oct 2023 02:24:36 +0000 (UTC) Received: by smtp.kernel.org (Postfix) with ESMTPSA id BE8A9C433C7; Tue, 24 Oct 2023 02:24:35 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=kernel.org; s=k20201202; t=1698114276; bh=b07IW6onHHyGfMZgKFIvnNFhOtkZkOOgJ9t2POWbmRs=; h=Date:From:To:Cc:Subject:In-Reply-To:References:From; b=oy3/JmEHd9Z4kheIA9EKM6UApScmCdcCisvBFeijpylMGB9icb/ybF52szjNEsFNK BsDsG6dV6iarpwc9ZpoPPBdwWYgB41lj5TEae4bLE8kbQEcHkip9FzEN+b4KLUPeNi i/7kjU2HPzxUEnOtIVHsNSjxXqYT2aqUe0rZg7IWJjhpVtiGthUOTgkYhdBN5UcnZv CYMNlJRywkXhSd7ef0W1v2d8kqo/XIiSKIOQfYCIuiU88NDnmL9ZDP0q6HfH/XS1NA h+J821kmQdxrA/lY5pS3jvkT49rmvS8t0X1TMWLmV2TK+lFExT0LGsNX76dS73YFZv 5h2gbbKLSqDZA== Date: Mon, 23 Oct 2023 19:24:34 -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 v12 0/5] introduce page_pool_alloc() related API Message-ID: <20231023192434.40f5ee98@kernel.org> In-Reply-To: <20231020095952.11055-1-linyunsheng@huawei.com> References: <20231020095952.11055-1-linyunsheng@huawei.com> MIME-Version: 1.0 X-CRM114-Version: 20100106-BlameMichelson ( TRE 0.8.0 (BSD) ) MR-646709E3 X-CRM114-CacheID: sfid-20231023_192438_042034_35F9A9E4 X-CRM114-Status: GOOD ( 13.69 ) X-BeenThere: linux-arm-kernel@lists.infradead.org X-Mailman-Version: 2.1.34 Precedence: list List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: "linux-arm-kernel" Errors-To: linux-arm-kernel-bounces+linux-arm-kernel=archiver.kernel.org@lists.infradead.org On Fri, 20 Oct 2023 17:59:47 +0800 Yunsheng Lin wrote: > In [1] & [2] & [3], there are usecases for veth and virtio_net > to use frag support in page pool to reduce memory usage, and it > may request different frag size depending on the head/tail > room space for xdp_frame/shinfo and mtu/packet size. When the > requested frag size is large enough that a single page can not > be split into more than one frag, using frag support only have > performance penalty because of the extra frag count handling > for frag support. > > So this patchset provides a page pool API for the driver to > allocate memory with least memory utilization and performance > penalty when it doesn't know the size of memory it need > beforehand. I don't mean to cut off the discussion, if any is still to happen. But AFAIU we have a general agreement that this is a good direction, we're at v12 already, and it's getting late in the release cycle. To give this series a chance of making v6.7 I will apply it now. If there are any unresolved concerns in a couple of days we can drop it. _______________________________________________ linux-arm-kernel mailing list linux-arm-kernel@lists.infradead.org http://lists.infradead.org/mailman/listinfo/linux-arm-kernel