From: Oliver Hartkopp <socketcan@hartkopp.net>
To: linux-can@vger.kernel.org
Cc: netdev@vger.kernel.org, sergei.shtylyov@cogentembedded.com,
Oliver Hartkopp <socketcan@hartkopp.net>
Subject: [RFC PATCH v3 0/2] can: join filters with per-CPU variables
Date: Wed, 1 Apr 2015 07:50:27 +0200 [thread overview]
Message-ID: <1427867429-3909-1-git-send-email-socketcan@hartkopp.net> (raw)
Hi all,
as Andre Naujoks found some problems in my first patches with multi-threading
I did some investigation how to handle variables to be written inside the
NET_RX softirq without locking. As far as I was able to test this code it works
properly now - even with the multi-thread test from Andre.
If you know how to use per-CPU variables inside NET_RX softirq I would
appreciate your review as I'm not that sure that the per-CPU code is correct.
It's my first time using this technique and is only what I was able to get from
other code examples and available kernel docs.
Many thanks,
Oliver
Changes v1 -> v2:
* Introduce per-CPU variables
Changes v2 -> v3:
* Fix style issues remarked by Sergei Shtylyov and Marc Kleine-Budde
* Indroduced a per-CPU struct as suggested by Marc Kleine-Budde
* omitted the obsolete per-CPU struct data initialization as alloc_percpu
provides already zero'ed memory
Oliver Hartkopp (2):
can: fix multiple delivery of a single CAN frame for overlapping CAN
filters
can: introduce new raw socket option to join the given CAN filters
Documentation/networking/can.txt | 20 ++++++++++++++--
include/uapi/linux/can/raw.h | 1 +
net/can/raw.c | 50 ++++++++++++++++++++++++++++++++++++++++
3 files changed, 69 insertions(+), 2 deletions(-)
--
2.1.4
next reply other threads:[~2015-04-01 5:50 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-04-01 5:50 Oliver Hartkopp [this message]
2015-04-01 5:50 ` [RFC PATCH v3 1/2] can: fix multiple delivery of a single CAN frame for overlapping CAN filters Oliver Hartkopp
2015-04-01 9:07 ` Marc Kleine-Budde
2015-04-01 9:44 ` Oliver Hartkopp
2015-04-01 9:46 ` Marc Kleine-Budde
2015-04-01 5:50 ` [RFC PATCH v3 2/2] can: introduce new raw socket option to join the given " Oliver Hartkopp
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=1427867429-3909-1-git-send-email-socketcan@hartkopp.net \
--to=socketcan@hartkopp.net \
--cc=linux-can@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=sergei.shtylyov@cogentembedded.com \
/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).