From: Conor Walsh <conor.walsh@intel.com>
To: Vladimir Medvedkin <vladimir.medvedkin@intel.com>, <dev@dpdk.org>
Cc: <konstantin.ananyev@intel.com>
Subject: Re: [dpdk-dev] [PATCH] fib: add rib extension size parameter
Date: Wed, 8 Sep 2021 17:59:38 +0100 [thread overview]
Message-ID: <ee9dce2f-3665-1a54-e217-839c0dbebc0c@intel.com> (raw)
In-Reply-To: <1630943759-362969-1-git-send-email-vladimir.medvedkin@intel.com>
> This patch adds a new parameter to the fib configuration to specify
> the size of the extension for internal RIB structure.
>
> Signed-off-by: Vladimir Medvedkin <vladimir.medvedkin@intel.com>
Tested-by: Conor Walsh <conor.walsh@intel.com>
next prev parent reply other threads:[~2021-09-08 17:01 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-09-06 15:55 Vladimir Medvedkin
2021-09-08 16:59 ` Conor Walsh [this message]
2021-10-25 17:23 ` Thomas Monjalon
2021-10-26 20:30 ` Medvedkin, Vladimir
2021-10-27 8:28 ` Thomas Monjalon
2021-10-27 15:47 ` Medvedkin, Vladimir
2021-10-27 15:49 ` [dpdk-dev] [PATCH v2] " Vladimir Medvedkin
2021-11-04 11:36 ` Thomas Monjalon
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=ee9dce2f-3665-1a54-e217-839c0dbebc0c@intel.com \
--to=conor.walsh@intel.com \
--cc=dev@dpdk.org \
--cc=konstantin.ananyev@intel.com \
--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).