Hello Alex.
On 13.06.22 05:29, Alexander Aring wrote:
In nhc we have compression() and uncompression(). Currently we have a
limitation that we return -EEXIST when it's the nhc is already
registered according the nexthdr. But on receiving handling and the
nhcid we can indeed support both at the same time.
The sentence above is not really clear to me. Do you want to say that on
rx we can support more than one nhcid? I am a bit confused why you write
both here. Where does the limit to two come from?
We remove the current
static array implementation and replace it by a dynamic list handling to
get rid of this limitation.
Signed-off-by: Alexander Aring <aahringo@xxxxxxxxxx>
---
net/6lowpan/nhc.c | 69 ++++++++++++++++++++++++++++++-----------------
1 file changed, 44 insertions(+), 25 deletions(-)
diff --git a/net/6lowpan/nhc.c b/net/6lowpan/nhc.c
index 7b374595328d..3d7c50139142 100644
--- a/net/6lowpan/nhc.c
+++ b/net/6lowpan/nhc.c
@@ -12,13 +12,30 @@
#include "nhc.h"
-static const struct lowpan_nhc *lowpan_nexthdr_nhcs[NEXTHDR_MAX + 1];
+struct lowpan_nhc_entry {
+ const struct lowpan_nhc *nhc;
+ struct list_head list;
+};
+
static DEFINE_SPINLOCK(lowpan_nhc_lock);
+static LIST_HEAD(lowpan_nexthdr_nhcs);
+
+const struct lowpan_nhc *lowpan_nhc_by_nexthdr(u8 nexthdr)
+{
+ const struct lowpan_nhc_entry *e;
+
+ list_for_each_entry(e, &lowpan_nexthdr_nhcs, list) {
+ if (e->nhc->nexthdr == nexthdr &&
+ e->nhc->compress)
+ return e->nhc;
We will always go with the first one we find? Do I miss something or
does that mean the one registered as seond and above will never be taken
into acount?
regards
Stefan Schmidt
