All of lore.kernel.org
 help / color / mirror / Atom feed
From: Alexander Aring <aahringo@redhat.com>
To: jukka.rissanen@linux.intel.com
Cc: linux-bluetooth@vger.kernel.org, linux-wpan@vger.kernel.org,
	stefan@datenfreihafen.org, torvalds@linuxfoundation.org
Subject: [PATCH bluetooth-next 0/3] net: 6lowpan: simplify lookup by nhc id
Date: Wed, 27 Apr 2022 23:05:31 -0400	[thread overview]
Message-ID: <20220428030534.3220410-1-aahringo@redhat.com> (raw)

Hi,

this patch series removes the rb data structure for looking up a nhc by
nhc id. Instead we using the existing nexthdr lookup array by iterating
over it and find the right nhc by nhc id. It's simply not worth it to
use such complex handling for such small amount of nhc. As we only
support nhc ids which fits into 1 byte and there are not two byte nhc
ids values specified yet, we let the nhc layer only handle 1 byte values.
If there is the need for 2 byte nhc values we can add support for it.

- Alex

Alexander Aring (3):
  net: 6lowpan: remove const from scalars
  net: 6lowpan: use array for find nhc id
  net: 6lowpan: constify lowpan_nhc structures

 net/6lowpan/nhc.c               | 103 ++++++--------------------------
 net/6lowpan/nhc.h               |  38 +++++-------
 net/6lowpan/nhc_dest.c          |   9 +--
 net/6lowpan/nhc_fragment.c      |   9 +--
 net/6lowpan/nhc_ghc_ext_dest.c  |   9 +--
 net/6lowpan/nhc_ghc_ext_frag.c  |  11 +---
 net/6lowpan/nhc_ghc_ext_hop.c   |   9 +--
 net/6lowpan/nhc_ghc_ext_route.c |   9 +--
 net/6lowpan/nhc_ghc_icmpv6.c    |   9 +--
 net/6lowpan/nhc_ghc_udp.c       |   9 +--
 net/6lowpan/nhc_hop.c           |   9 +--
 net/6lowpan/nhc_ipv6.c          |  11 +---
 net/6lowpan/nhc_mobility.c      |   9 +--
 net/6lowpan/nhc_routing.c       |   9 +--
 net/6lowpan/nhc_udp.c           |   9 +--
 15 files changed, 48 insertions(+), 214 deletions(-)

-- 
2.31.1


             reply	other threads:[~2022-04-28  3:06 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-04-28  3:05 Alexander Aring [this message]
2022-04-28  3:05 ` [PATCH bluetooth-next 1/3] net: 6lowpan: remove const from scalars Alexander Aring
2022-04-28  3:47   ` net: 6lowpan: simplify lookup by nhc id bluez.test.bot
2022-05-02 19:36   ` [PATCH bluetooth-next 1/3] net: 6lowpan: remove const from scalars Stefan Schmidt
2022-05-03  7:31   ` Jukka Rissanen
2022-04-28  3:05 ` [PATCH bluetooth-next 2/3] net: 6lowpan: use array for find nhc id Alexander Aring
2022-05-02 19:37   ` Stefan Schmidt
2022-05-03  7:32   ` Jukka Rissanen
2022-04-28  3:05 ` [PATCH bluetooth-next 3/3] net: 6lowpan: constify lowpan_nhc structures Alexander Aring
2022-05-02 19:37   ` Stefan Schmidt
2022-05-03  7:32   ` Jukka Rissanen
2022-06-01 20:28 ` [PATCH bluetooth-next 0/3] net: 6lowpan: simplify lookup by nhc id Stefan Schmidt
2022-06-01 21:48   ` Luiz Augusto von Dentz
2022-06-01 21:56     ` Stefan Schmidt
2022-06-01 21:58       ` Luiz Augusto von Dentz
2022-06-02 15:27         ` Marcel Holtmann
2022-06-02 17:38           ` Stefan Schmidt
2022-06-02 17:41 ` Stefan Schmidt

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=20220428030534.3220410-1-aahringo@redhat.com \
    --to=aahringo@redhat.com \
    --cc=jukka.rissanen@linux.intel.com \
    --cc=linux-bluetooth@vger.kernel.org \
    --cc=linux-wpan@vger.kernel.org \
    --cc=stefan@datenfreihafen.org \
    --cc=torvalds@linuxfoundation.org \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.