DPDK patches and discussions
 help / color / mirror / Atom feed
From: "Varghese, Vipin" <Vipin.Varghese@amd.com>
To: "Bruce Richardson" <bruce.richardson@intel.com>,
	"Morten Brørup" <mb@smartsharesystems.com>
Cc: "dev@dpdk.org" <dev@dpdk.org>,
	"anatoly.burakov@intel.com" <anatoly.burakov@intel.com>
Subject: RE: [PATCH] net/intel: allow fast-free to empty cache
Date: Mon, 9 Jun 2025 05:12:57 +0000	[thread overview]
Message-ID: <PH7PR12MB85964A4F15AF14E7486EE85D826BA@PH7PR12MB8596.namprd12.prod.outlook.com> (raw)
In-Reply-To: <Z-a3ELVHCCbvyDIl@bricha3-mobl1.ger.corp.intel.com>

[Public]

Snipped

> > > When freeing transmitted mbufs, there is no reason to send the freed
> > > mbufs directly to the ring if the cache is empty - only if it is
> > > zero size (in which case the cache pointer is NULL). Therefore,
> > > remove the empty check and only check for a null cache pointer.
> > >
> > > Signed-off-by: Bruce Richardson <bruce.richardson@intel.com>
> > > ---
> > >  drivers/net/intel/common/tx.h | 2 +-
> > >  1 file changed, 1 insertion(+), 1 deletion(-)
> > >
> > > diff --git a/drivers/net/intel/common/tx.h
> > > b/drivers/net/intel/common/tx.h index d9cf4474fc..d361fe64ab 100644
> > > --- a/drivers/net/intel/common/tx.h
> > > +++ b/drivers/net/intel/common/tx.h
> > > @@ -143,7 +143,7 @@ ci_tx_free_bufs_vec(struct ci_tx_queue *txq,
> > > ci_desc_done_fn desc_done, bool ctx
> > >             void **cache_objs;
> > >             struct rte_mempool_cache *cache =
> > > rte_mempool_default_cache(mp, rte_lcore_id());
> > >
> > > -           if (!cache || cache->len == 0)
> > > +           if (cache == NULL)
> > >                     goto normal;
> > >
> > >             cache_objs = &cache->objs[cache->len];
> > > --
> > > 2.43.0
> >
> > Yep, it did look strange.
> > Reviewed-by: Morten Brørup <mb@smartsharesystems.com>
> >
> Applied to dpdk-next-net-intel.

Reviewed-by: Vipin.Varghese@amd.com
Tested-by: Thiyagarajan.P@amd.com

At AMD we tested the code change on the platform `AMD Siena EPYC 8534P using Intel E810 2CQDA2`.

- simd: AVX512
- TEST: DPDK-TESTPMD in tx mode
- cmd: `./dpdk-testpmd -l 15,16,17 --force-max-simd-bitwidth=512 -a c1:00.0 -a c1:00.1 -- -i --nb-cores=2 --nb-ports=2 --rxq=1 --txq=1 --rxd=1024 --txd=1024 --forward-mode=txonly -a`
- Before vs After
-- TX-RX Desc 1024, TX-RX 1Q: 117.12, 117.13
-- TX-RX Desc 1024, TX-RX 2Q: 117.13, 117.17
-- TX-RX Desc 2048, TX-RX 1Q: 117.16, 117.18
-- TX-RX Desc 2048, TX-RX 2Q: 117.13, 117.15

>
> /Bruce

      reply	other threads:[~2025-06-09  5:13 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-02-21 16:58 Intel FAST_FREE offload question Morten Brørup
2025-02-21 17:09 ` Bruce Richardson
2025-02-21 17:16   ` Morten Brørup
2025-03-10 13:25 ` [PATCH] net/intel: allow fast-free to empty cache Bruce Richardson
2025-03-10 15:18   ` Morten Brørup
2025-03-10 15:27     ` Bruce Richardson
2025-03-10 15:34       ` Morten Brørup
2025-03-10 15:53         ` Bruce Richardson
2025-03-10 17:37           ` Morten Brørup
2025-03-28 14:49     ` Bruce Richardson
2025-06-09  5:12       ` Varghese, Vipin [this message]

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=PH7PR12MB85964A4F15AF14E7486EE85D826BA@PH7PR12MB8596.namprd12.prod.outlook.com \
    --to=vipin.varghese@amd.com \
    --cc=anatoly.burakov@intel.com \
    --cc=bruce.richardson@intel.com \
    --cc=dev@dpdk.org \
    --cc=mb@smartsharesystems.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).