DPDK patches and discussions
 help / color / mirror / Atom feed
From: Thomas Monjalon <thomas@monjalon.net>
To: Vladimir Medvedkin <vladimir.medvedkin@intel.com>
Cc: dev@dpdk.org, john.mcnamara@intel.com, marko.kovacevic@intel.com,
	stable@dpdk.org, bruce.richardson@intel.com,
	konstantin.ananyev@intel.com, david.marchand@redhat.com
Subject: Re: [dpdk-dev] [PATCH] doc: add rib and fib into the API doxygen index
Date: Mon, 06 Jul 2020 21:31:25 +0200	[thread overview]
Message-ID: <5194699.pna8TFVyyh@thomas> (raw)
In-Reply-To: <adbdb54b39da9dd39bd744add425fb215b17e58c.1594054765.git.vladimir.medvedkin@intel.com>

06/07/2020 19:00, Vladimir Medvedkin:
> Add RIB/FIB library into the API doxygen index.
> Move LPM/LPM6 under separate section "Longest prefix match"
[...]
> --- a/doc/api/doxy-api-index.md
> +++ b/doc/api/doxy-api-index.md
>  - **QoS**:
> @@ -116,6 +114,14 @@ The public API headers are grouped by topics:
>    [scheduler]          (@ref rte_sched.h),
>    [RED congestion]     (@ref rte_red.h)
>  
> +- **Longest prefix match**:

I would have thought to "routing" as title of this section.
Is "longest prefix match" better?

> +  [LPM IPv4 route]     (@ref rte_lpm.h),
> +  [LPM IPv6 route]     (@ref rte_lpm6.h),
> +  [RIB IPv4]           (@ref rte_rib.h),
> +  [RIB IPv6]           (@ref rte_rib6.h),
> +  [FIB IPv4]           (@ref rte_fib.h),
> +  [FIB IPv6]           (@ref rte_fib6.h)
> +
>  - **hashes**:
>    [hash]               (@ref rte_hash.h),
>    [jhash]              (@ref rte_jhash.h),





  reply	other threads:[~2020-07-06 19:31 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-07-06 17:00 Vladimir Medvedkin
2020-07-06 19:31 ` Thomas Monjalon [this message]
2020-07-08 13:56   ` Medvedkin, Vladimir
2020-07-08 14:25     ` Thomas Monjalon
2020-07-08 18:31 ` [dpdk-dev] [PATCH v2] " Vladimir Medvedkin
2020-07-10 21:35   ` 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=5194699.pna8TFVyyh@thomas \
    --to=thomas@monjalon.net \
    --cc=bruce.richardson@intel.com \
    --cc=david.marchand@redhat.com \
    --cc=dev@dpdk.org \
    --cc=john.mcnamara@intel.com \
    --cc=konstantin.ananyev@intel.com \
    --cc=marko.kovacevic@intel.com \
    --cc=stable@dpdk.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).