From: "Varghese, Vipin" <vipin.varghese@intel.com>
To: Ophir Munk <ophirmu@mellanox.com>, "dev@dpdk.org" <dev@dpdk.org>,
"Yigit, Ferruh" <ferruh.yigit@intel.com>,
"Wiles, Keith" <keith.wiles@intel.com>
Cc: Thomas Monjalon <thomas@monjalon.net>, Olga Shern <olgas@mellanox.com>
Subject: Re: [dpdk-dev] [PATCH v3] net/tap: perform proto field update for tun only
Date: Wed, 23 May 2018 04:37:31 +0000 [thread overview]
Message-ID: <4C9E0AB70F954A408CC4ADDBF0F8FA7D4D1F880F@BGSMSX101.gar.corp.intel.com> (raw)
In-Reply-To: <HE1PR0501MB2314E160250F8BD48BCE11C4D1940@HE1PR0501MB2314.eurprd05.prod.outlook.com>
Hi Ophir,
Thanks for inputs, please find my answers inline to the mail
> -----Original Message-----
> From: Ophir Munk [mailto:ophirmu@mellanox.com]
> Sent: Tuesday, May 22, 2018 8:35 PM
> To: Varghese, Vipin <vipin.varghese@intel.com>; dev@dpdk.org; Yigit, Ferruh
> <ferruh.yigit@intel.com>; Wiles, Keith <keith.wiles@intel.com>
> Cc: Thomas Monjalon <thomas@monjalon.net>; Olga Shern
> <olgas@mellanox.com>
> Subject: RE: [PATCH v3] net/tap: perform proto field update for tun only
>
> Hi,
> Overall it looks good.
> Please note a few more comments below.
>
> > -----Original Message-----
> > From: Vipin Varghese [mailto:vipin.varghese@intel.com]
> > Sent: Tuesday, May 22, 2018 1:47 PM
> > To: dev@dpdk.org; ferruh.yigit@intel.com; keith.wiles@intel.com; Ophir
> > Munk <ophirmu@mellanox.com>
> > Cc: Thomas Monjalon <thomas@monjalon.net>; Olga Shern
> > <olgas@mellanox.com>; Vipin Varghese <vipin.varghese@intel.com>
> > Subject: [PATCH v3] net/tap: perform proto field update for tun only
> >
> > The TX function is shared between TAP and TUN PMD. Checking TUN-TAP
> > type field will ensure the TAP PMD will always have protocol field as 0.
> >
> > Signed-off-by: Vipin Varghese <vipin.varghese@intel.com>
> > Suggested-by: Ferruh Yigit <ferruh.yigit@intel.com>
> > ---
>
> Shouldn't it be a fix commit?
The following code base is not merged with stable, dev or next-net branch. Hence do we 'fix commit' this?
> If so - please update the commit title, add Fixes: ... , Cc: stable@dpdk.org...
>
> > Changes in V3:
> > - remove type field from rx struct - Ophir Munk
> > - add space for comment in struct - Ophir Munk
> > - pass type field into eth_dev_tap_create - Ophir Munk
> > - replace with enum value for type - Ophir Munk
> > - return as 'not supported' for mac_set - Vipin Varghese
> >
> > Changes in V2:
> > - updated in comment wording - Keith Wiles
> > - remove debug print from tx code - Keith Wiles
> > ---
> > drivers/net/tap/rte_eth_tap.c | 61
> > +++++++++++++++++++++++++-------------
> > -----
> > drivers/net/tap/rte_eth_tap.h | 9 +++++++
> > 2 files changed, 45 insertions(+), 25 deletions(-)
> >
<Snipped>
> >
> > + if (pmd->type == ETH_TUNTAP_TYPE_TUN)
> > + return -ENOTSUP;
>
>
> Can you please add a TAP_LOG(ERR, ...) to log this error similar to other error
> cases in this function?
Yes, I will add the change in v4 and share the same.
>
> > +
<Snipped>
next prev parent reply other threads:[~2018-05-23 4:37 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-05-14 4:53 [dpdk-dev] [PATCH] " Vipin Varghese
2018-05-14 22:27 ` Wiles, Keith
2018-05-15 9:08 ` Varghese, Vipin
2018-05-15 14:49 ` [dpdk-dev] [PATCH v2] " Vipin Varghese
2018-05-15 12:31 ` Wiles, Keith
2018-05-15 22:28 ` Ophir Munk
2018-05-22 6:33 ` Varghese, Vipin
2018-05-22 11:05 ` Varghese, Vipin
2018-05-22 13:55 ` Wiles, Keith
2018-05-22 10:47 ` [dpdk-dev] [PATCH v3] " Vipin Varghese
2018-05-22 13:53 ` Wiles, Keith
2018-05-23 4:33 ` Varghese, Vipin
2018-05-22 15:04 ` Ophir Munk
2018-05-23 4:37 ` Varghese, Vipin [this message]
2018-05-22 22:04 ` [dpdk-dev] [PATCH v4] " Ferruh Yigit
2018-05-22 22:06 ` Ferruh Yigit
2018-05-22 22:09 ` [dpdk-dev] [PATCH v5] net/tap: fix proto field for tun Ferruh Yigit
2018-05-22 22:19 ` Ferruh Yigit
2018-05-22 22:25 ` Ferruh Yigit
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=4C9E0AB70F954A408CC4ADDBF0F8FA7D4D1F880F@BGSMSX101.gar.corp.intel.com \
--to=vipin.varghese@intel.com \
--cc=dev@dpdk.org \
--cc=ferruh.yigit@intel.com \
--cc=keith.wiles@intel.com \
--cc=olgas@mellanox.com \
--cc=ophirmu@mellanox.com \
--cc=thomas@monjalon.net \
/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).