From: Rami Rosen <roszenrami@gmail.com>
To: Saleh Alsouqi <salehals@mellanox.com>
Cc: wenzhuo.lu@intel.com, jingjing.wu@intel.com,
bernard.iremonger@intel.com, dev@dpdk.org,
Ori Kam <orika@mellanox.com>,
stable@dpdk.org
Subject: Re: [dpdk-stable] [dpdk-dev] [PATCH] app/testpmd: fix mpls encap ipv4 version and ihl
Date: Tue, 25 Dec 2018 21:29:12 +0200 [thread overview]
Message-ID: <CAKoUArnYfH3q8Mm0zSGVbyAtpe2Yhn_W1O1dVDJ6UJF1mhAmrw@mail.gmail.com> (raw)
In-Reply-To: <1545136604-22816-1-git-send-email-salehals@mellanox.com>
Hi Saleh,
Thanks for your patch.
If you will grep into the DPDK repo you will see that there are several
occurrences of IP_VHL_DEF, with the same functionality.
I would consider putting the IPV4_VHL_DEF you added in a more generic
location and not
under testpmd, so other modules will be able to use it without the need to
include testpmd.h, which is a bit awkard.
Another question is whether it should be IPV4_VHL_DEF or IPV_VHL_DEF as in
other DPDK apps. Probably other apps should be adjusted to use it.
Regards,
Rami Rosen
next prev parent reply other threads:[~2018-12-25 19:29 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-12-18 12:36 [dpdk-stable] " Saleh Alsouqi
2018-12-25 19:29 ` Rami Rosen [this message]
2019-01-08 14:38 ` [dpdk-stable] [dpdk-dev] " Ferruh Yigit
2019-03-25 13:01 ` [dpdk-stable] [PATCH v2] " Saleh Alsouqi
2019-03-25 13:30 ` Ferruh Yigit
2019-04-16 9:59 ` Ferruh Yigit
2019-04-16 10:02 ` [dpdk-stable] [dpdk-dev] " Ferruh Yigit
2019-07-02 13:33 ` Yigit, Ferruh
2019-07-04 7:33 ` [dpdk-stable] [PATCH v3 0/2] define ipv4 ihl and vhl Saleh Alsouqi
2019-07-04 7:33 ` [dpdk-stable] [PATCH v3 1/2] librte_net/rte_ip: " Saleh Alsouqi
2019-07-04 7:33 ` [dpdk-stable] [PATCH v3 2/2] app/testpmd: fix mpls ipv4 encap fields Saleh Alsouqi
2019-07-04 16:19 ` [dpdk-stable] [PATCH v3 0/2] define ipv4 ihl and vhl 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=CAKoUArnYfH3q8Mm0zSGVbyAtpe2Yhn_W1O1dVDJ6UJF1mhAmrw@mail.gmail.com \
--to=roszenrami@gmail.com \
--cc=bernard.iremonger@intel.com \
--cc=dev@dpdk.org \
--cc=jingjing.wu@intel.com \
--cc=orika@mellanox.com \
--cc=salehals@mellanox.com \
--cc=stable@dpdk.org \
--cc=wenzhuo.lu@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).