From: "Wang, Xiao W" <xiao.w.wang@intel.com>
To: Thomas Monjalon <thomas.monjalon@6wind.com>
Cc: "dev@dpdk.org" <dev@dpdk.org>
Subject: Re: [dpdk-dev] [PATCH v4 1/3] fm10k: enable FTAG based forwarding
Date: Tue, 1 Mar 2016 11:06:36 +0000 [thread overview]
Message-ID: <B7F2E978279D1D49A3034B7786DACF403DBADED5@SHSMSX101.ccr.corp.intel.com> (raw)
In-Reply-To: <1785217.K8F1c8amTK@xps13>
> -----Original Message-----
> From: Thomas Monjalon [mailto:thomas.monjalon@6wind.com]
> Sent: Tuesday, March 1, 2016 3:36 PM
> To: Wang, Xiao W <xiao.w.wang@intel.com>
> Cc: dev@dpdk.org; Chen, Jing D <jing.d.chen@intel.com>
> Subject: Re: [dpdk-dev] [PATCH v4 1/3] fm10k: enable FTAG based forwarding
>
> 2016-03-01 13:36, Wang Xiao W:
> > +static int
> > +fm10k_check_ftag(struct rte_devargs *devargs) {
> > + if (devargs == NULL)
> > + return 0;
> > +
> > + if (strstr(devargs->args, "enable_ftag=1") == NULL)
> > + return 0;
> > +
> > + return 1;
> > +}
>
> With strstr(), chenable_ftag=12 will work :) Please check how to use kvargs.
OK, it's better to standardize the args string processing. I'll rework it.
Best Regards,
Xiao
next prev parent reply other threads:[~2016-03-01 11:06 UTC|newest]
Thread overview: 52+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-01-25 8:07 [dpdk-dev] [PATCH 0/3] " Wang Xiao W
2016-01-25 8:07 ` [dpdk-dev] [PATCH 1/3] " Wang Xiao W
2016-02-02 3:07 ` Qiu, Michael
2016-02-02 10:03 ` Wang, Xiao W
2016-02-02 10:50 ` [dpdk-dev] [PATCH v2 0/3] " Wang Xiao W
2016-02-02 10:50 ` [dpdk-dev] [PATCH v2 1/3] " Wang Xiao W
2016-02-03 6:52 ` Chen, Jing D
2016-02-04 2:39 ` Wang, Xiao W
2016-02-04 3:38 ` [dpdk-dev] [PATCH v3 0/3] " Wang Xiao W
2016-02-04 3:38 ` [dpdk-dev] [PATCH v3 1/3] " Wang Xiao W
2016-02-24 15:42 ` Bruce Richardson
2016-02-24 16:37 ` Thomas Monjalon
2016-02-24 17:05 ` Bruce Richardson
2016-02-25 10:04 ` Chen, Jing D
2016-02-25 13:35 ` Bruce Richardson
2016-02-25 15:45 ` Chen, Jing D
2016-02-25 16:14 ` Bruce Richardson
2016-02-26 4:31 ` Wang, Xiao W
2016-02-26 9:06 ` Thomas Monjalon
2016-02-26 9:24 ` Wang, Xiao W
2016-02-26 14:48 ` Bruce Richardson
2016-02-26 15:00 ` David Marchand
2016-02-26 16:33 ` Bruce Richardson
2016-02-29 1:47 ` Wang, Xiao W
2016-02-26 20:48 ` Thomas Monjalon
2016-03-01 5:36 ` [dpdk-dev] [PATCH v4 0/3] " Wang Xiao W
2016-03-01 5:36 ` [dpdk-dev] [PATCH v4 1/3] " Wang Xiao W
2016-03-01 7:35 ` Thomas Monjalon
2016-03-01 11:06 ` Wang, Xiao W [this message]
2016-03-01 22:37 ` Stephen Hemminger
2016-03-02 6:05 ` Wang, Xiao W
2016-03-02 13:47 ` Thomas Monjalon
2016-03-02 11:19 ` [dpdk-dev] [PATCH v5 0/2] " Wang Xiao W
2016-03-02 11:19 ` [dpdk-dev] [PATCH v5 1/2] " Wang Xiao W
2016-03-10 16:32 ` Bruce Richardson
2016-03-02 11:19 ` [dpdk-dev] [PATCH v5 2/2] doc: add introduction for fm10k " Wang Xiao W
2016-03-08 7:57 ` [dpdk-dev] [PATCH v5 0/2] fm10k: enable " Liu, Yong
2016-03-10 3:34 ` Wang, Xiao W
2016-03-10 16:40 ` Bruce Richardson
2016-03-01 5:36 ` [dpdk-dev] [PATCH v4 2/3] doc: add introduction for fm10k " Wang Xiao W
2016-03-01 5:36 ` [dpdk-dev] [PATCH v4 3/3] doc: update release note for fm10k FTAG support Wang Xiao W
2016-02-04 3:38 ` [dpdk-dev] [PATCH v3 2/3] doc: add introduction for fm10k FTAG based forwarding Wang Xiao W
2016-02-22 14:06 ` Mcnamara, John
2016-02-04 3:38 ` [dpdk-dev] [PATCH v3 3/3] doc: update release note for fm10k FTAG support Wang Xiao W
2016-02-22 13:51 ` Mcnamara, John
2016-02-04 9:47 ` [dpdk-dev] [PATCH v3 0/3] fm10k: enable FTAG based forwarding Chen, Jing D
2016-02-02 10:50 ` [dpdk-dev] [PATCH v2 2/3] doc: add introduction for fm10k " Wang Xiao W
2016-02-02 10:50 ` [dpdk-dev] [PATCH v2 3/3] doc: update release note for fm10k FTAG support Wang Xiao W
2016-01-25 8:07 ` [dpdk-dev] [PATCH 2/3] doc: add introduction for fm10k FTAG based forwarding Wang Xiao W
2016-01-25 8:07 ` [dpdk-dev] [PATCH 3/3] doc: update release note for fm10k FTAG support Wang Xiao W
2016-02-01 16:20 ` Mcnamara, John
2016-01-26 6:01 ` [dpdk-dev] [PATCH 0/3] fm10k: enable FTAG based forwarding Liu, Yong
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=B7F2E978279D1D49A3034B7786DACF403DBADED5@SHSMSX101.ccr.corp.intel.com \
--to=xiao.w.wang@intel.com \
--cc=dev@dpdk.org \
--cc=thomas.monjalon@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).