From: Alexander Aring <alex.aring@gmail.com>
To: Michael Richardson <mcr@sandelman.ca>
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: Sat, 14 Nov 2015 10:20:42 +0100 [thread overview]
Message-ID: <20151114092040.GA1652@omega> (raw)
In-Reply-To: <26774.1447438082@sandelman.ca>
Hi Michael,
On Fri, Nov 13, 2015 at 01:08:02PM -0500, Michael Richardson wrote:
>
> 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.
>
ok, thanks.
> 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.
>
Do you want to have this per interface or overall? We could make both.
For the lock-less part a per-cpu counter would be fit here, it will
summarize then all counters per-cpu if they will be requested.
- Alex
prev parent reply other threads:[~2015-11-14 9:20 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
2015-11-14 9:20 ` Alexander Aring [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=20151114092040.GA1652@omega \
--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=martin.gergeleit@hs-rm.de \
--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 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.