diff options
| author | Ondrej Zajicek <santiago@crfreenet.org> | 2023-10-02 15:09:30 +0200 |
|---|---|---|
| committer | Ondrej Zajicek <santiago@crfreenet.org> | 2023-10-02 15:09:30 +0200 |
| commit | 21213be523baa7f2cbf0feaa617f265c55e9b17a (patch) | |
| tree | 97d0374225e267fe6b3c0cc64eacbe5395ba00b6 /nest/rt-attr.c | |
| parent | 8ad9c4bb339172d445d1346876b2c9f3c27199c1 (diff) | |
Nest: Expand rte_src.private_id to u64
In general, private_id is sparse and protocols may want to map some
internal values directly into it. For example, L3VPN needs to
map VPN route discriminators to private_id.
OTOH, u32 is enough for global_id, as these identifiers are dense.
Diffstat (limited to 'nest/rt-attr.c')
| -rw-r--r-- | nest/rt-attr.c | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/nest/rt-attr.c b/nest/rt-attr.c index b341ff46..9e29abc8 100644 --- a/nest/rt-attr.c +++ b/nest/rt-attr.c @@ -101,7 +101,7 @@ static struct idm src_ids; #define RSH_KEY(n) n->proto, n->private_id #define RSH_NEXT(n) n->next #define RSH_EQ(p1,n1,p2,n2) p1 == p2 && n1 == n2 -#define RSH_FN(p,n) p->hash_key ^ u32_hash(n) +#define RSH_FN(p,n) p->hash_key ^ u64_hash(n) #define RSH_REHASH rte_src_rehash #define RSH_PARAMS /2, *2, 1, 1, 8, 20 |