DPDK patches and discussions
 help / color / mirror / Atom feed
From: Bruce Richardson <bruce.richardson@intel.com>
To: Muhammad Ahmad <muhammad.ahmad@emumba.com>
Cc: dev@dpdk.org, ferruh.yigit@intel.com, qi.z.zhang@intel.com,
	konstantin.ananyev@intel.com, jia.guo@intel.com,
	beilei.xing@intel.com
Subject: Re: [dpdk-dev] [RFC] Add selection between vector and scalar mode in ixgbe
Date: Tue, 25 May 2021 10:22:45 +0100	[thread overview]
Message-ID: <YKzB5UkIy5ortOMZ@bricha3-MOBL.ger.corp.intel.com> (raw)
In-Reply-To: <20210525065818.10379-1-muhammad.ahmad@emumba.com>

On Tue, May 25, 2021 at 11:58:18AM +0500, Muhammad Ahmad wrote:
> 
> The selection between scalar mode and vector mode was removed for
> ixgbe driver in DPDK 20.02. The code base still has code
> for scalar mode but it cannot be selected at compile time. The
> vector mode is adequate for applications which require high
> throughput which is the case most of the time, but scalar mode has
> a use case in ultra-low-latency fintech applications for algorithmic
> trading. This use case was also presented at the DPDK userspace
> summit in September 2020.
> This patch enables the ability to select between scalar and vector
> modes for ixgbe drivers in the config.
> In the future we can introduce API in ehtdev, which allow user to
> select between latency and throughput mode.  
> 
> Signed-off-by: Muhammad Ahmad <muhammad.ahmad@emumba.com>
> ---
Rather than having compile-time selection, this should be supported via
runtime selection, using the force-max-simd-bitwidth flag. Setting the flag
to 64 should force scalar paths.

Regards,
/Bruce

      reply	other threads:[~2021-05-25  9:22 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-05-25  6:58 Muhammad Ahmad
2021-05-25  9:22 ` Bruce Richardson [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=YKzB5UkIy5ortOMZ@bricha3-MOBL.ger.corp.intel.com \
    --to=bruce.richardson@intel.com \
    --cc=beilei.xing@intel.com \
    --cc=dev@dpdk.org \
    --cc=ferruh.yigit@intel.com \
    --cc=jia.guo@intel.com \
    --cc=konstantin.ananyev@intel.com \
    --cc=muhammad.ahmad@emumba.com \
    --cc=qi.z.zhang@intel.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).