From: Stephen Hemminger <stephen@networkplumber.org>
To: Rami Rosen <roszenrami@gmail.com>
Cc: "Thomas Monjalon" <thomas@monjalon.net>,
"Morten Brørup" <mb@smartsharesystems.com>,
dev@dpdk.org, olivier.matz@6wind.com, arybchenko@solarflare.com,
ferruh.yigit@intel.com
Subject: Re: [RFC] function to parse packet headers
Date: Thu, 10 Jan 2019 16:11:58 -0800 [thread overview]
Message-ID: <20190110161158.0177a203@hermes.lan> (raw)
In-Reply-To: <CAKoUAr=xAnUY4xjDD2wv5dEmonEHHknK_rbO3DJeiMdCKiSfgQ@mail.gmail.com>
On Thu, 10 Jan 2019 03:03:24 +0200
Rami Rosen <roszenrami@gmail.com> wrote:
> Hi, Morten,
>
> > And regarding avoiding code duplicity, I'm pursuing Olivier about merging
> packet header validation into rte_net_get_ptype() instead of writing a
> separate function.
> >
> This seems also a good alternative.
> +1
>
> Regards,
> Rami Rosen
>
+1
All drivers that don't have hardware support for getting l2/l3 and ptype
information should be calling rte_net_get_ptype() already.
next prev parent reply other threads:[~2019-01-11 0:12 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-08 16:48 [RFC] function to parse packet headers Morten Brørup
2019-01-08 20:09 ` Rami Rosen
2019-01-09 15:53 ` Morten Brørup
2019-01-09 23:57 ` Thomas Monjalon
2019-01-10 1:03 ` Rami Rosen
2019-01-11 0:11 ` Stephen Hemminger [this message]
2019-01-11 7:56 ` Andrew Rybchenko
2019-01-11 8:16 ` Morten Brørup
2019-01-11 8:28 ` Andrew Rybchenko
2019-01-11 8:35 ` Olivier Matz
2019-01-11 9:49 ` Ananyev, Konstantin
2019-01-11 12:04 ` Morten Brørup
-- strict thread matches above, loose matches on Subject: below --
2019-01-09 3:43 longtb5
2019-01-09 15:38 ` Morten Brørup
2019-01-10 3:25 ` longtb5
2019-01-10 8:21 ` Morten Brørup
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=20190110161158.0177a203@hermes.lan \
--to=stephen@networkplumber.org \
--cc=arybchenko@solarflare.com \
--cc=dev@dpdk.org \
--cc=ferruh.yigit@intel.com \
--cc=mb@smartsharesystems.com \
--cc=olivier.matz@6wind.com \
--cc=roszenrami@gmail.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.