From: Jakub Kicinski <kuba@kernel.org>
To: Yunsheng Lin <linyunsheng@huawei.com>
Cc: <davem@davemloft.net>, <pabeni@redhat.com>,
<netdev@vger.kernel.org>, <linux-kernel@vger.kernel.org>,
Alexander Duyck <alexander.duyck@gmail.com>,
Andrew Morton <akpm@linux-foundation.org>, <linux-mm@kvack.org>
Subject: Re: [PATCH net-next v5 01/13] mm: page_frag: add a test module for page_frag
Date: Wed, 29 May 2024 17:29:38 -0700 [thread overview]
Message-ID: <20240529172938.3a83784d@kernel.org> (raw)
In-Reply-To: <20240528125604.63048-2-linyunsheng@huawei.com>
On Tue, 28 May 2024 20:55:51 +0800 Yunsheng Lin wrote:
> Basing on the lib/objpool.c, change it to something like a
> ptrpool, so that we can utilize that to test the correctness
> and performance of the page_frag.
>
> The testing is done by ensuring that the fragments allocated
> from a frag_frag_cache instance is pushed into a ptrpool
> instance in a kthread binded to a specified cpu, and a kthread
> binded to a specified cpu will pop the fragmemt from the
fragment
> ptrpool and free the fragmemt.
>
> We may refactor out the common part between objpool and ptrpool
> if this ptrpool thing turns out to be helpful for other place.
Is this test actually meaningfully testing page_frag or rather
the objpool construct and the scheduler? :S
next prev parent reply other threads:[~2024-05-30 0:29 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20240528125604.63048-1-linyunsheng@huawei.com>
2024-05-28 12:55 ` Yunsheng Lin
2024-05-30 0:29 ` Jakub Kicinski [this message]
2024-05-30 9:17 ` Yunsheng Lin
2024-05-30 15:16 ` Jakub Kicinski
2024-05-31 8:50 ` Yunsheng Lin
2024-05-28 12:55 ` [PATCH net-next v5 03/13] mm: page_frag: use free_unref_page() to free page fragment Yunsheng Lin
2024-05-28 12:55 ` [PATCH net-next v5 04/13] mm: move the page fragment allocator from page_alloc into its own file Yunsheng Lin
2024-05-28 12:55 ` [PATCH net-next v5 05/13] mm: page_frag: use initial zero offset for page_frag_alloc_align() Yunsheng Lin
2024-05-28 12:55 ` [PATCH net-next v5 06/13] mm: page_frag: add '_va' suffix to page_frag API Yunsheng Lin
2024-05-28 12:55 ` [PATCH net-next v5 07/13] mm: page_frag: avoid caller accessing 'page_frag_cache' directly Yunsheng Lin
2024-05-28 12:55 ` [PATCH net-next v5 08/13] mm: page_frag: reuse existing space for 'size' and 'pfmemalloc' Yunsheng Lin
2024-05-28 12:56 ` [PATCH net-next v5 10/13] mm: page_frag: introduce prepare/probe/commit API Yunsheng Lin
2024-05-30 9:21 ` Yunsheng Lin
2024-05-28 12:56 ` [PATCH net-next v5 12/13] mm: page_frag: update documentation for page_frag Yunsheng Lin
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20240529172938.3a83784d@kernel.org \
--to=kuba@kernel.org \
--cc=akpm@linux-foundation.org \
--cc=alexander.duyck@gmail.com \
--cc=davem@davemloft.net \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=linyunsheng@huawei.com \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox