DPDK-dev Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Sun Yuechi <sunyuechi@iscas.ac.cn>
To: Vladimir Medvedkin <vladimir.medvedkin@intel.com>
Cc: dev@dpdk.org, Sun Yuechi <sunyuechi@iscas.ac.cn>
Subject: [PATCH 0/2] fib: fix and speed up RVV lookup
Date: Mon,  5 Oct 2026 00:04:44 -0700	[thread overview]
Message-ID: <cover.1791183388.git.sunyuechi@iscas.ac.cn> (raw)

Patch 1 fixes wrong next hops from a FIB created with
RTE_FIB_F_LOOKUP_NETWORK_ORDER on RISC-V: the vector lookup read the
addresses in host order.

Patch 2 removes a register spill from the vector lookup loop by
gathering the entries at the width they are stored with.

Patch 2, ns per lookup, standalone benchmark, tables in cache, -O3:

                    1B     2B     4B     8B
  SpacemiT X60
    before         31.1   32.1   30.6   29.7
    after          27.2   27.9   27.6   26.4
  Sophgo SG2044
    before          5.6    5.7    5.9    7.5
    after           4.4    4.1    5.0    6.0
  SpacemiT X100
    before          4.7    4.8    4.8    5.9
    after           4.1    4.2    4.3    5.1

fib_perf_autotest, whose addresses miss the cache, gains 0 to 14%.

Sun Yuechi (2):
  fib: fix lookup in network order with RVV
  fib: gather entries at their own width with RVV

 lib/fib/dir24_8.c     |  4 +-
 lib/fib/dir24_8_rvv.c | 85 ++++++++++++++++++++++++-------------------
 2 files changed, 49 insertions(+), 40 deletions(-)

-- 
2.56.0


             reply	other threads:[~2026-10-05  7:04 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-10-05  7:04 Sun Yuechi [this message]
2026-10-05  7:04 ` [PATCH 1/2] fib: fix lookup in network order with RVV Sun Yuechi
2026-10-05  7:04 ` [PATCH 2/2] fib: gather entries at their own width " Sun Yuechi

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=cover.1791183388.git.sunyuechi@iscas.ac.cn \
    --to=sunyuechi@iscas.ac.cn \
    --cc=dev@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