From: Yunsheng Lin <linyunsheng@huawei.com>
To: Ratheesh Kannoth <rkannoth@marvell.com>, <netdev@vger.kernel.org>,
<linux-kernel@vger.kernel.org>
Cc: <sgoutham@marvell.com>, <davem@davemloft.net>,
<edumazet@google.com>, <kuba@kernel.org>, <pabeni@redhat.com>,
<sbhatta@marvell.com>, <gakula@marvell.com>,
<schalla@marvell.com>, <hkelam@marvell.com>
Subject: Re: [PATCH net-next v2] octeontx2-pf: Add support for page pool
Date: Fri, 19 May 2023 09:41:30 +0800 [thread overview]
Message-ID: <9b576dd4-6083-9fab-5859-875287831d0a@huawei.com> (raw)
In-Reply-To: <20230518055129.3129897-1-rkannoth@marvell.com>
On 2023/5/18 13:51, Ratheesh Kannoth wrote:
> Page pool for each rx queue enhance rx side performance
> by reclaiming buffers back to each queue specific pool. DMA
> mapping is done only for first allocation of buffers.
> As subsequent buffers allocation avoid DMA mapping,
> it results in performance improvement.
>
> Image | Performance with Linux kernel Packet Generator
Is there any more detailed info for the performance data?
'kernel Packet Generator' means using pktgen module in the
net/core/pktgen.c? it seems pktgen is more for tx, is there
any abvious reason why the page pool optimization for rx have
brought about ten times improvement?
> ------------ | -----------------------------------------------
> Vannila | 3Mpps
> |
> with this | 42Mpps
> change |
> -------------------------------------------------------------
>
...
> static int __otx2_alloc_rbuf(struct otx2_nic *pfvf, struct otx2_pool *pool,
> dma_addr_t *dma)
> {
> u8 *buf;
>
> + if (pool->page_pool)
> + return otx2_alloc_pool_buf(pfvf, pool, dma);
> +
> buf = napi_alloc_frag_align(pool->rbsize, OTX2_ALIGN);
> if (unlikely(!buf))
> return -ENOMEM;
It seems the above is dead code when using 'select PAGE_POOL', as
PAGE_POOL config is always selected by the driver?
> @@ -1205,10 +1226,28 @@ void otx2_sq_free_sqbs(struct otx2_nic *pfvf)
> }
> }
>
...
> @@ -1659,7 +1715,6 @@ int otx2_nix_config_bp(struct otx2_nic *pfvf, bool enable)
> req->bpid_per_chan = 0;
> #endif
>
> -
Nit: unrelated change here.
> return otx2_sync_mbox_msg(&pfvf->mbox);
> }
next prev parent reply other threads:[~2023-05-19 1:41 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-18 5:51 Ratheesh Kannoth
2023-05-19 1:41 ` Yunsheng Lin [this message]
2023-05-19 1:52 ` Ratheesh Kannoth
2023-05-19 2:37 ` Yunsheng Lin
2023-05-19 5:19 ` [EXT] " Sunil Kovvuri Goutham
2023-05-19 5:30 ` Ratheesh Kannoth
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=9b576dd4-6083-9fab-5859-875287831d0a@huawei.com \
--to=linyunsheng@huawei.com \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=gakula@marvell.com \
--cc=hkelam@marvell.com \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=rkannoth@marvell.com \
--cc=sbhatta@marvell.com \
--cc=schalla@marvell.com \
--cc=sgoutham@marvell.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
all inboxes | Powered by JetHome®