On Tue, 22 Oct 2024 18:37:09 +
Wathsala Wathawana Vithanage wrote:
> > 2. The API's should be used in the drivers and core, not exposed up
> > to the application. Most of the hot data structures are in the
> > drivers now.
> >
> PMDs don't know which CPU and cache level to use
Hi Stephen,
> There is a fundamental conflict with the increasing growth of "nerd knobs"
> like this in the DPDK. Users already have problems understanding DPDK and
> adding more complexity does not help.
>
> So any new feature like this should be:
> 1. Just work right without any configuration
> -Original Message-
> From: Chenbo Xia
> Sent: Monday, October 21, 2024 2:35 AM
> To: Wathsala Wathawana Vithanage
> Cc: dev@dpdk.org; nd
> Subject: Re: [RFC v3 0/2] An API for Stashing Packets into CPU caches
>
> Hi,
>
> > On Oct 21, 2024, at 0
Hi,
> On Oct 21, 2024, at 09:52, Wathsala Vithanage
> wrote:
>
> External email: Use caution opening links or attachments
>
>
> DPDK applications benefit from Direct Cache Access (DCA) features like
> Intel DDIO and Arm's write-allocate-to-SLC. However, those features do
> not allow fine-grai
DPDK applications benefit from Direct Cache Access (DCA) features like
Intel DDIO and Arm's write-allocate-to-SLC. However, those features do
not allow fine-grained control of direct cache access, such as stashing
packets into upper-level caches (L2 caches) of a processor or the shared
cache of a c
5 matches
Mail list logo
