From: David Marchand <david.marchand@redhat.com>
To: Vladimir Medvedkin <vladimir.medvedkin@intel.com>
Cc: Stephen Hemminger <stephen@networkplumber.org>,
dev@dpdk.org, rjarry@redhat.com, mb@smartsharesystems.com
Subject: Re: [PATCH v5] fib: network byte order IPv4 lookup
Date: Mon, 14 Oct 2024 18:59:11 +0200 [thread overview]
Message-ID: <CAJFAV8zZQjbVuXbZB1sj4wn4z7EAqs-N1R1q==LTGT8YLa_cAg@mail.gmail.com> (raw)
In-Reply-To: <20241014082237.7d8ca276@hermes.local>
On Mon, Oct 14, 2024 at 5:22 PM Stephen Hemminger
<stephen@networkplumber.org> wrote:
> On Mon, 14 Oct 2024 13:37:07 +0000
> Vladimir Medvedkin <vladimir.medvedkin@intel.com> wrote:
>
> > Previously when running rte_fib_lookup IPv4 addresses must have been in
> > host byte order.
> >
> > This patch adds a new flag RTE_FIB_FLAG_LOOKUP_BE that can be passed on
> > fib create, which will allow to have IPv4 in network byte order on
> > lookup.
> >
> > Signed-off-by: Vladimir Medvedkin <vladimir.medvedkin@intel.com>
> Acked-by: Stephen Hemminger <stephent@networkplumber.org>
I aligned the meson bits to other libraries (passing cc_avx512_flags),
and changed internal flags field into an unsigned int (like the field
coming from the configuration structure).
Applied, thanks Vladimir.
--
David Marchand
prev parent reply other threads:[~2024-10-14 16:59 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-09-06 17:06 [PATCH] " Vladimir Medvedkin
2024-09-27 23:51 ` David Marchand
2024-09-30 15:07 ` David Marchand
2024-10-04 12:01 ` Vladimir Medvedkin
2024-10-08 17:33 ` [PATCH v2] " Vladimir Medvedkin
2024-10-10 11:26 ` [PATCH v3] " Vladimir Medvedkin
2024-10-11 10:32 ` Robin Jarry
2024-10-11 11:29 ` David Marchand
2024-10-11 14:33 ` David Marchand
2024-10-11 17:57 ` [PATCH v4] " Vladimir Medvedkin
2024-10-14 13:37 ` [PATCH v5] " Vladimir Medvedkin
2024-10-14 15:22 ` Stephen Hemminger
2024-10-14 16:59 ` David Marchand [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='CAJFAV8zZQjbVuXbZB1sj4wn4z7EAqs-N1R1q==LTGT8YLa_cAg@mail.gmail.com' \
--to=david.marchand@redhat.com \
--cc=dev@dpdk.org \
--cc=mb@smartsharesystems.com \
--cc=rjarry@redhat.com \
--cc=stephen@networkplumber.org \
--cc=vladimir.medvedkin@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).