From: Honnappa Nagarahalli <Honnappa.Nagarahalli@arm.com>
To: "Morten Brørup" <mb@smartsharesystems.com>,
"Feifei Wang" <Feifei.Wang2@arm.com>,
"Yuying Zhang" <Yuying.Zhang@intel.com>,
"Beilei Xing" <beilei.xing@intel.com>,
"Ruifeng Wang" <Ruifeng.Wang@arm.com>
Cc: "dev@dpdk.org" <dev@dpdk.org>, nd <nd@arm.com>,
Konstantin Ananyev <konstantin.v.ananyev@yandex.ru>,
Olivier Matz <olivier.matz@6wind.com>, nd <nd@arm.com>
Subject: RE: [RFC PATCH v1] net/i40e: put mempool cache out of API
Date: Wed, 22 Jun 2022 19:07:33 +0000 [thread overview]
Message-ID: <DBAPR08MB581464128C9A728ADE414E8098B29@DBAPR08MB5814.eurprd08.prod.outlook.com> (raw)
In-Reply-To: <98CBD80474FA8B44BF855DF32C47DC35D87117@smartserver.smartshare.dk>
<snip>
> Subject: RE: [RFC PATCH v1] net/i40e: put mempool cache out of API
>
> > From: Feifei Wang [mailto:feifei.wang2@arm.com]
> > Sent: Monday, 13 June 2022 07.52
> >
> > Refer to "i40e_tx_free_bufs_avx512", this patch puts mempool cache out
> > of API to free buffers directly. There are two changes different with
> > previous version:
> > 1. change txep from "i40e_entry" to "i40e_vec_entry"
> > 2. put cache out of "mempool_bulk" API to copy buffers into it
> > directly
> >
> > Performance Test with l3fwd neon path:
> > with this patch
> > n1sdp: no perforamnce change
> > amper-altra: +4.0%
> >
> > Suggested-by: Konstantin Ananyev <konstantin.v.ananyev@yandex.ru>
> > Suggested-by: Honnappa Nagarahalli <honnappa.nagarahalli@arm.com>
> > Signed-off-by: Feifei Wang <feifei.wang2@arm.com>
> > ---
>
> Once again bypassing the mempool API and copy-pasting internal code from
> the mempool library to a PMD for performance optimization.
>
> Certainly not happy about it, but it's already done elsewhere, and thus we
> should not deny it here...
>
> Acked-by: Morten Brørup <mb@smartsharesystems.com>
This was done with the intention to understand the performance of the zero-copy mempool APIs that Konstantin suggested. Even though this patch does not have the zero-copy mempool APIs, it reflects the code/instructions of creating such as API. We are trying to show here that zero-copy mempool APIs will not provide equivalent performance of direct-rearm method.
next prev parent reply other threads:[~2022-06-22 19:07 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-13 5:51 Feifei Wang
2022-06-13 9:58 ` Morten Brørup
2022-06-22 19:07 ` Honnappa Nagarahalli [this message]
2022-07-03 12:20 ` Konstantin Ananyev
2022-07-06 8:52 ` 回复: " Feifei Wang
2022-07-06 11:35 ` Feifei Wang
2022-07-11 3:08 ` Feifei Wang
2022-07-11 6:19 ` Honnappa Nagarahalli
2022-07-13 18:48 ` Konstantin Ananyev
2022-07-15 21:52 ` Honnappa Nagarahalli
2022-07-21 10:02 ` Konstantin Ananyev
2022-07-15 22:06 ` Honnappa Nagarahalli
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=DBAPR08MB581464128C9A728ADE414E8098B29@DBAPR08MB5814.eurprd08.prod.outlook.com \
--to=honnappa.nagarahalli@arm.com \
--cc=Feifei.Wang2@arm.com \
--cc=Ruifeng.Wang@arm.com \
--cc=Yuying.Zhang@intel.com \
--cc=beilei.xing@intel.com \
--cc=dev@dpdk.org \
--cc=konstantin.v.ananyev@yandex.ru \
--cc=mb@smartsharesystems.com \
--cc=nd@arm.com \
--cc=olivier.matz@6wind.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;
as well as URLs for NNTP newsgroup(s).