From: Michael Richardson <mcr@sandelman.ca>
To: Alexander Aring <alex.aring@gmail.com>
Cc: linux-wpan@vger.kernel.org, linux-bluetooth@vger.kernel.org,
kernel@pengutronix.de, lukasz.duda@nordicsemi.no,
martin.gergeleit@hs-rm.de
Subject: Re: [RFC bluetooth-next 4/4] 6lowpan: iphc: add support for stateful compression
Date: Fri, 13 Nov 2015 13:08:02 -0500 [thread overview]
Message-ID: <26774.1447438082@sandelman.ca> (raw)
In-Reply-To: <1447262079-2509-5-git-send-email-alex.aring@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 677 bytes --]
These patches are very nice to have, I will attempt to test them out.
I am waiting for a JTAG programmer to unwedge my openmote, and then I'll
put RIOT on that, but in the meantime I'll be testing against Contiki
on Econotag.
One thing that I wanted to add was a counter per type of HC header decoded.
I seemed to recall that the was some RCU-ish way to do lock-less 64-bit
counters, but I haven't tracked down the right reference.
--
] Never tell me the odds! | ipv6 mesh networks [
] Michael Richardson, Sandelman Software Works | network architect [
] mcr@sandelman.ca http://www.sandelman.ca/ | ruby on rails [
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 481 bytes --]
next prev parent reply other threads:[~2015-11-13 18:13 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-11-11 17:14 [RFC bluetooth-next 0/4] 6lowpan: debugfs and stateful compression support Alexander Aring
2015-11-11 17:14 ` [RFC bluetooth-next 1/4] 6lowpan: add debugfs support Alexander Aring
2015-11-12 17:04 ` Alexander Aring
2015-11-11 17:14 ` [RFC bluetooth-next 2/4] 6lowpan: iphc: add check for reserved values Alexander Aring
2015-11-11 17:14 ` [RFC bluetooth-next 3/4] 6lowpan: iphc: remove handling when dam is zero Alexander Aring
2015-11-11 17:14 ` [RFC bluetooth-next 4/4] 6lowpan: iphc: add support for stateful compression Alexander Aring
2015-11-13 18:08 ` Michael Richardson [this message]
2015-11-14 9:20 ` Alexander Aring
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=26774.1447438082@sandelman.ca \
--to=mcr@sandelman.ca \
--cc=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=martin.gergeleit@hs-rm.de \
/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;
as well as URLs for NNTP newsgroup(s).