All of lore.kernel.org
 help / color / mirror / Atom feed
From: Stefan Schmidt <stefan@osg.samsung.com>
To: Alexander Aring <alex.aring@gmail.com>
Cc: linux-wpan@vger.kernel.org,
	Jukka Rissanen <jukka.rissanen@linux.intel.com>,
	linux-bluetooth@vger.kernel.org
Subject: Re: [PATCH v2 bluetooth-next 0/7] GHC compression detection
Date: Fri, 27 Nov 2015 13:30:55 +0100	[thread overview]
Message-ID: <56584CFF.9030306@osg.samsung.com> (raw)
In-Reply-To: <20151127121330.GA28084@omega>

Hello.

On 27/11/15 13:13, Alexander Aring wrote:
> On Wed, Nov 25, 2015 at 03:59:10PM +0100, Stefan Schmidt wrote:
>> Hello.
>>
>> This is a first stab at RFC7400. So far we only hook into the NHC framework to
>> detect the registered GHC types (extension headers, UDP and ICMPv6).
>> This is aligned with how we detect the NHC frames.
>>
> TODO for next is to make possible that we can load multiple nhc modules
> for the transmit side. We have a 1(tranmit):n(receive) mapping here, and
> we should support all nhc's for receive side.
>
> For tranmsmit side we should have a disable by default and offer a
> debugfs entry (nhc framework debugfs support) to enable/disable it
> at runtime. It's a 1:nexhdr mapping, so only one for nexthdr can running
> at the same time currently. If somebody tries that it should be return
> -EBUSY.
>
> I would suggest additional patches:
>
> 1. Allow to have register everything and disable compression methods of
>     all nhcs by default. The receive handling should always possible,
>     the compression should be disabled by default because other 6LoWPAN
>     stacks may not support e.g. GHC types.
>
>     Maybe we can do a nhc directory for the debugfs interface related entry
>     for that. So the nhc framework offers some support e.g. enable compression
>     for nhc xy.
>
> 2. Add all you nhc's _after_ all other nhc modules. This will occur that
>     the first ones has a higher priority. Our priority strategy is then
>     like the order of the list. See [0].
>
> 3. Add "default y" to all nhc's for support receiving always.
>
>
> That's huge work, but maybe the next steps.

Yes, I will tackle them with the next set. I'm working on the actual 
compression and decrompression code for GHC at the moment. Once that is 
working I will tackle the items you listed above and put them together 
in one patchset.
> Otherwise it's looking good and let the NHC framework as first known
> about these next header compressions, so:
>
> Acked-by: Alexander Aring <alex.aring@gmail.com>

Thanks. I think with your and Jukka's ACK this set would be ready to land.


      reply	other threads:[~2015-11-27 12:30 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-11-25 14:59 [PATCH v2 bluetooth-next 0/7] GHC compression detection Stefan Schmidt
2015-11-25 14:59 ` [PATCH v2 bluetooth-next 1/7] 6lowpan: clarify Kconfig entries for upcoming GHC support Stefan Schmidt
2015-11-25 14:59 ` [PATCH v2 bluetooth-next 2/7] 6lowpan: add nhc module for GHC hop-by-hopextension header detection Stefan Schmidt
2015-11-25 14:59 ` [PATCH v2 bluetooth-next 3/7] 6lowpan: add nhc module for GHC UDP detection Stefan Schmidt
2015-11-25 14:59 ` [PATCH v2 bluetooth-next 4/7] 6lowpan: add nhc module for GHC ICMPv6 detection Stefan Schmidt
2015-11-25 14:59 ` [PATCH v2 bluetooth-next 5/7] 6lowpan: add nhc module for GHC destination extension header detection Stefan Schmidt
2015-11-25 14:59 ` [PATCH v2 bluetooth-next 6/7] 6lowpan: add nhc module for GHC fragmentation " Stefan Schmidt
2015-11-25 14:59 ` [PATCH v2 bluetooth-next 7/7] 6lowpan: add nhc module for GHC routing " Stefan Schmidt
2015-11-25 15:18 ` [PATCH v2 bluetooth-next 0/7] GHC compression detection Jukka Rissanen
2015-11-27 12:13 ` Alexander Aring
2015-11-27 12:30   ` Stefan Schmidt [this message]

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=56584CFF.9030306@osg.samsung.com \
    --to=stefan@osg.samsung.com \
    --cc=alex.aring@gmail.com \
    --cc=jukka.rissanen@linux.intel.com \
    --cc=linux-bluetooth@vger.kernel.org \
    --cc=linux-wpan@vger.kernel.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.