From: Thomas Monjalon <thomas@monjalon.net>
To: Bruce Richardson <bruce.richardson@intel.com>
Cc: dev@dpdk.org, Qiaobin Fu <qiaobinf@bu.edu>,
michel@digirati.com.br, doucette@bu.edu
Subject: Re: [dpdk-dev] [PATCH] LPM: add iterator over LPM rules
Date: Sun, 28 Oct 2018 11:24:14 +0100 [thread overview]
Message-ID: <21111006.6ffmIrYtWP@xps> (raw)
In-Reply-To: <20180708214606.124420-1-qiaobinf@bu.edu>
08/07/2018 23:46, Qiaobin Fu:
> Add an iterator over the LPM rules.
> The iterator requires a prefix as a parameter and
> lists all entries as long as the given prefix (or longer).
>
> Signed-off-by: Qiaobin Fu <qiaobinf@bu.edu>
> Reviewed-by: Cody Doucette <doucette@bu.edu>
> Reviewed-by: Michel Machado <michel@digirati.com.br>
Any news about this patch?
next prev parent reply other threads:[~2018-10-28 10:24 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-07-08 21:46 Qiaobin Fu
2018-10-28 10:24 ` Thomas Monjalon [this message]
2018-10-28 16:45 ` Fu, Qiaobin
2023-06-09 16:57 ` Stephen Hemminger
2023-06-09 16:59 ` [PATCH 1/2] eal/bitmap: support bitmap reverse scanning Stephen Hemminger
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=21111006.6ffmIrYtWP@xps \
--to=thomas@monjalon.net \
--cc=bruce.richardson@intel.com \
--cc=dev@dpdk.org \
--cc=doucette@bu.edu \
--cc=michel@digirati.com.br \
--cc=qiaobinf@bu.edu \
/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).