From: Ferruh Yigit <ferruh.yigit@intel.com>
To: "Nélio Laranjeiro" <nelio.laranjeiro@6wind.com>,
"Shahaf Shuler" <shahafs@mellanox.com>
Cc: adrien.mazarguil@6wind.com, dev@dpdk.org
Subject: Re: [dpdk-dev] [PATCH v2 1/2] net/mlx5: modify PMD args process
Date: Wed, 19 Apr 2017 13:40:36 +0100 [thread overview]
Message-ID: <9fd5e784-cebd-a742-d1da-6252c10c9d66@intel.com> (raw)
In-Reply-To: <20170419065053.GL14075@autoinstall.dev.6wind.com>
On 4/19/2017 7:50 AM, Nélio Laranjeiro wrote:
> On Tue, Apr 18, 2017 at 01:22:27PM +0300, Shahaf Shuler wrote:
>> Currently the argument process is done without indication which
>> parameter was forced by the application and which one is on it
>> default value.
>> This becomes problematic when different features requires different
>> defaults. For example, Enhanced multi packet send and TSO.
>>
>> This commit modifies the argument process, enabling to differ
>> which parameter was forced by the application.
>>
>> Signed-off-by: Shahaf Shuler <shahafs@mellanox.com>
>> Acked-by: Yongseok Koh <yskoh@mellanox.com>
> For the series,
>
> Acked-by: Nelio Laranjeiro <nelio.laranjeiro@6wind.com>
Series applied to dpdk-next-net/master, thanks.
prev parent reply other threads:[~2017-04-19 12:40 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-04-16 7:46 [dpdk-dev] [PATCH " Shahaf Shuler
2017-04-16 7:46 ` [dpdk-dev] [PATCH 2/2] net/mlx5: fix PMD specific parameters defaults Shahaf Shuler
2017-04-18 6:49 ` [dpdk-dev] [PATCH 1/2] net/mlx5: modify PMD args process Nélio Laranjeiro
2017-04-18 10:22 ` [dpdk-dev] [PATCH v2 " Shahaf Shuler
2017-04-18 10:22 ` [dpdk-dev] [PATCH v2 2/2] net/mlx5: fix PMD specific parameters defaults Shahaf Shuler
2017-04-19 10:57 ` Ferruh Yigit
2017-04-19 11:32 ` Shahaf Shuler
2017-04-19 12:25 ` Ferruh Yigit
2017-04-19 12:31 ` Shahaf Shuler
2017-04-19 6:50 ` [dpdk-dev] [PATCH v2 1/2] net/mlx5: modify PMD args process Nélio Laranjeiro
2017-04-19 12:40 ` Ferruh Yigit [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=9fd5e784-cebd-a742-d1da-6252c10c9d66@intel.com \
--to=ferruh.yigit@intel.com \
--cc=adrien.mazarguil@6wind.com \
--cc=dev@dpdk.org \
--cc=nelio.laranjeiro@6wind.com \
--cc=shahafs@mellanox.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).