DPDK patches and discussions
 help / color / mirror / Atom feed
From: "Robin Jarry" <rjarry@redhat.com>
To: "Vladimir Medvedkin" <vladimir.medvedkin@intel.com>
Cc: "Thomas Monjalon" <thomas@monjalon.net>, <dev@dpdk.org>,
	"Bruce Richardson" <bruce.richardson@intel.com>
Subject: fib/rib: allow storing void * instead of nexthop index
Date: Wed, 31 Jul 2024 17:04:32 +0200	[thread overview]
Message-ID: <D33TEQPTXPBU.1Z9S7W669X59U@redhat.com> (raw)

Hi Vladimir,

I noticed that the fib/rib APIs (both IPv4 and IPv6) require the next 
hops to be represented as integer indexes. Reading the code, I noticed 
that they are stored as uint64_t with the MSB used for internal 
purposes.

This require either having a contiguous array of nexthop objects and 
choose an index in that array, or store pointer offsets as nexthop 
indexes and do pointer arithmetics to reconstruct the real pointers. 
Both are not very practical and/or hacky.

Would it be possible to store arbitrary pointers? That would mean 
moving that 64th bit information elsewhere.

I'd love to hear what you think on the matter.

Cheers,
Robin


             reply	other threads:[~2024-07-31 15:05 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-07-31 15:04 Robin Jarry [this message]
2024-07-31 15:53 ` Medvedkin, Vladimir

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=D33TEQPTXPBU.1Z9S7W669X59U@redhat.com \
    --to=rjarry@redhat.com \
    --cc=bruce.richardson@intel.com \
    --cc=dev@dpdk.org \
    --cc=thomas@monjalon.net \
    --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).