From: Thomas Monjalon <thomas@monjalon.net>
To: Nelio Laranjeiro <nelio.laranjeiro@6wind.com>
Cc: dev@dpdk.org, Ferruh Yigit <ferruh.yigit@intel.com>
Subject: Re: [dpdk-dev] [PATCH v2] net/mlx5: add parameters to enable/disable vector code
Date: Thu, 03 Aug 2017 23:36:47 +0200 [thread overview]
Message-ID: <1664208.49YYPCpkqG@xps> (raw)
In-Reply-To: <fdfdc6b19d092d67a3fa4d324a8c3f96d37cdd16.1501687792.git.nelio.laranjeiro@6wind.com>
02/08/2017 17:32, Nelio Laranjeiro:
> Vector code is very young and can present some issues for users, to avoid
> them to modify the selections function by commenting the code and recompile
> the PMD, new devices parameters are added to deactivate the Tx and/or Rx
> vector code.
> By using such device parameters, the user will be able to fall back to
> regular burst functions.
>
> Signed-off-by: Nelio Laranjeiro <nelio.laranjeiro@6wind.com>
> Acked-by: Yongseok Koh <yskoh@mellanox.com>
Applied, thanks
prev parent reply other threads:[~2017-08-03 21:36 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-08-01 8:05 [dpdk-dev] [PATCH 0/5] net/mlx5: enable/disable vPMD and some cleanups Nelio Laranjeiro
2017-08-01 8:05 ` [dpdk-dev] [PATCH 1/5] net/mlx5: warn which Tx/Rx burst function is selected Nelio Laranjeiro
2017-08-01 8:05 ` [dpdk-dev] [PATCH 2/5] net/mlx5: add parameters to enable/disable vector code Nelio Laranjeiro
2017-08-01 8:05 ` [dpdk-dev] [PATCH 3/5] net/mlx5: avoid reusing old queue's mbuf on reconfigure Nelio Laranjeiro
2017-08-01 8:05 ` [dpdk-dev] [PATCH 4/5] net/mlx5: prepare vector Rx ring at setup time Nelio Laranjeiro
2017-08-01 8:05 ` [dpdk-dev] [PATCH 5/5] net/mlx5: cleanup Rx ring in free functions Nelio Laranjeiro
2017-08-02 15:32 ` [dpdk-dev] [PATCH v2] net/mlx5: enable/disable vPMD and some cleanups Nelio Laranjeiro
2017-08-02 15:32 ` [dpdk-dev] [PATCH v2] net/mlx5: add parameters to enable/disable vector code Nelio Laranjeiro
2017-08-03 21:36 ` Thomas Monjalon [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=1664208.49YYPCpkqG@xps \
--to=thomas@monjalon.net \
--cc=dev@dpdk.org \
--cc=ferruh.yigit@intel.com \
--cc=nelio.laranjeiro@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).