Linux bluetooth development
 help / color / mirror / Atom feed
From: Alexander Aring <alex.aring@gmail.com>
To: linux-wpan@vger.kernel.org
Cc: linux-bluetooth@vger.kernel.org, kernel@pengutronix.de,
	mcr@sandelman.ca, lukasz.duda@nordicsemi.no,
	Alexander Aring <alex.aring@gmail.com>
Subject: [PATCH bluetooth-next 0/2] 6lowpan: stateful compression support
Date: Sun, 10 Jan 2016 21:50:23 +0100	[thread overview]
Message-ID: <1452459025-13884-1-git-send-email-alex.aring@gmail.com> (raw)

Hi,

this contains at first some small fix for the netdev notifier which I deteced
while hacking 6lowpan stateful compression support.

I rework the debugfs entry for the stateful compression. Now each context entry
for a 6LoWPAN contains has his own subdirectory (named as his CID value).
In this subdirectories there exists the following files for manipulating the
context entry:

 - active: If the context belongs to the table or not.
 - compression: the compression flag according rfc6775.
 - prefix: ipv6 prefix in xxxx:xxxx:....:xxxx form.
 - prefix_lenght: the length of the ipv6 prefix.

This offers a setting per property instead doing remember the full context and
doing echo "$FULL_CONTEXT_INFORMATION" > ctx_table.

These file should be prepared to move into the sysfs directory when it seems to
running fine.

There exist one file "show" inside $LOWPAN_IFACE/contexts/. This file is for
a "pretty-printout" for the current context table. I use the same format-string
like RIOT-OS, example:

cid|prefix                                     |C
-------------------------------------------------
  0|                                 2001::/64 |1
  1|                                2001::1/128|1
  2|                                2001::5/128|1
  7|                                 2002::/64 |1


difference here is that RIOT shows the lifetime, but I currently see no sense to
handle the lifetime in kernelspace.

Also I added support to clean the context table when doing a "ifdown". The reason
is that IPv6 interface will also drop all address information while doing a
ifdown and a 6LoWPAN should not use previous context information after ifup again.

- Alex

Alexander Aring (2):
  6lowpan: iphc: add support for stateful compression
  ieee802154: 6lowpan: fix return of netdev notifier

 include/net/6lowpan.h         |  31 ++++
 net/6lowpan/core.c            |  39 +++-
 net/6lowpan/debugfs.c         | 247 +++++++++++++++++++++++++
 net/6lowpan/iphc.c            | 420 ++++++++++++++++++++++++++++++++++++------
 net/ieee802154/6lowpan/core.c |   7 +-
 5 files changed, 682 insertions(+), 62 deletions(-)

-- 
2.6.1


             reply	other threads:[~2016-01-10 20:50 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-01-10 20:50 Alexander Aring [this message]
2016-01-10 20:50 ` [PATCH bluetooth-next 1/2] 6lowpan: iphc: add support for stateful compression Alexander Aring
2016-01-15 14:39   ` Stefan Schmidt
2016-01-19  9:12   ` Duda, Lukasz
2016-01-10 20:50 ` [PATCH bluetooth-next 2/2] ieee802154: 6lowpan: fix return of netdev notifier Alexander Aring
2016-01-15 14:39   ` Stefan Schmidt
2016-01-19  9:05 ` [PATCH bluetooth-next 0/2] 6lowpan: stateful compression support Duda, Lukasz

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=1452459025-13884-1-git-send-email-alex.aring@gmail.com \
    --to=alex.aring@gmail.com \
    --cc=kernel@pengutronix.de \
    --cc=linux-bluetooth@vger.kernel.org \
    --cc=linux-wpan@vger.kernel.org \
    --cc=lukasz.duda@nordicsemi.no \
    --cc=mcr@sandelman.ca \
    /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