DPDK usage discussions
 help / color / mirror / Atom feed
From: neeraj.sj@satyaki.co.in
To: "Anantharam, Arjun" <arjun.anantharam@intel.com>
Cc: users@dpdk.org
Subject: Re: [ICE DPDK 21.11] Latency bump at certain rate
Date: Tue, 11 Jan 2022 04:40:02 +0000	[thread overview]
Message-ID: <625bb48cfbe2cd48b7afc79a41f24120@satyaki.co.in> (raw)
In-Reply-To: <MW3PR11MB4761E06FFB73CA9699DD1CE8804D9@MW3PR11MB4761.namprd11.prod.outlook.com>

On 2022-01-07 21:48, Anantharam, Arjun wrote:
> Hi,
> 
> I believe the suggestion here would be to try the new
> "rx_low_latency=1" option enabled with DPDK 21.11:
> 
>  ·        Low Rx latency (default 0)
> 
>  vRAN workloads require low latency DPDK interface for the front haul
> interface connection to Radio. By specifying 1 for parameter
> rx_low_latency, each completed Rx descriptor can be written
> immediately to host memory and the Rx interrupt latency can be reduced
> to 2us:
> 
> -a 0000:88:00.0,rx_low_latency=1
> 
>  As a trade-off, this configuration may cause the packet processing
> performance degradation due to the PCI bandwidth limitation.
> 
> If they are using an old DPDK version, they can try to backport below
> patch
> 
> http://patchwork.dpdk.org/project/dpdk/patch/20210924093429.12068-1-alvinx.zhang@intel.com/
> 
> 
> Thanks
Hi,
We are concerned about dropping the traffic, by limiting its rate to 22 
to 24 gbps, rather than allowing complete 40gbps, a formula for cir, 
pir, ebs and cbs would be more appreciated.
Thanks.

  reply	other threads:[~2022-01-11  4:40 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-01-07 21:48 Anantharam, Arjun
2022-01-11  4:40 ` neeraj.sj [this message]
  -- strict thread matches above, loose matches on Subject: below --
2021-12-21 12:47 Yueyang Pan

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=625bb48cfbe2cd48b7afc79a41f24120@satyaki.co.in \
    --to=neeraj.sj@satyaki.co.in \
    --cc=arjun.anantharam@intel.com \
    --cc=users@dpdk.org \
    /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).