From: Marc Kleine-Budde <mkl@pengutronix.de>
To: Oliver Hartkopp <socketcan@hartkopp.net>, linux-can@vger.kernel.org
Cc: netdev@vger.kernel.org
Subject: Re: [PATCH RFC v2 1/2] can: fix multiple delivery of a single CAN frame for overlapping CAN filters
Date: Mon, 30 Mar 2015 12:16:32 +0200 [thread overview]
Message-ID: <55192280.8090505@pengutronix.de> (raw)
In-Reply-To: <5519210E.40005@pengutronix.de>
[-- Attachment #1: Type: text/plain, Size: 1820 bytes --]
On 03/30/2015 12:10 PM, Marc Kleine-Budde wrote:
> On 03/29/2015 08:09 PM, Oliver Hartkopp wrote:
>> The CAN_RAW socket can set multiple CAN identifier specific filters that lead
>> to multiple filters in the af_can.c filter processing. These filters are
>> indenpendent from each other which leads to logical OR'ed filters when applied.
^
independent
>> This patch makes sure that every CAN frame which is filtered for a specific
>> socket is only delivered once to the user space. This is independent from the
>> number of matching CAN filters of this socket.
>>
>> As the can_raw() function is executed from NET_RX softirq the introduced
>> variables are implemented as per-CPU variables to avoid extensive locking at
>> CAN frame reception time.
>>
>> Signed-off-by: Oliver Hartkopp <socketcan@hartkopp.net>
>> + /* eliminate multiple filter matches for the same skb */
>> + if (*this_cpu_ptr(ro->uniq_skb) == oskb &&
>> + ktime_equal(*this_cpu_ptr(ro->uniq_tstamp), oskb->tstamp)) {
>> + return;
>> + } else {
>> + *this_cpu_ptr(ro->uniq_skb) = oskb;
>> + *this_cpu_ptr(ro->uniq_tstamp) = oskb->tstamp;
>> + }
>> +
>
> What happens if you're preempted somewhere in this code, it's not
> atomic? I think, if we only have to take care about the skb, an atomic
> compare exchange would work. But we have two variables....If you use a
> struct (see previous mail), I think the usage of get_cpu_ptr(),
> git_cpu_ptr() ensures that we're not preempted.
^^^^^^^^^^^^^
put_cpu_ptr()
Marc
--
Pengutronix e.K. | Marc Kleine-Budde |
Industrial Linux Solutions | Phone: +49-231-2826-924 |
Vertretung West/Dortmund | Fax: +49-5121-206917-5555 |
Amtsgericht Hildesheim, HRA 2686 | http://www.pengutronix.de |
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 819 bytes --]
next prev parent reply other threads:[~2015-03-30 10:16 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-03-29 18:09 [PATCH RFC v2 0/2] can: join filters with per-CPU variables Oliver Hartkopp
2015-03-29 18:09 ` [PATCH RFC v2 1/2] can: fix multiple delivery of a single CAN frame for overlapping CAN filters Oliver Hartkopp
2015-03-30 9:50 ` Marc Kleine-Budde
2015-03-30 10:29 ` Oliver Hartkopp
2015-03-30 10:36 ` Marc Kleine-Budde
2015-03-30 10:10 ` Marc Kleine-Budde
2015-03-30 10:16 ` Marc Kleine-Budde [this message]
2015-03-30 10:41 ` Oliver Hartkopp
2015-03-31 12:32 ` Marc Kleine-Budde
2015-03-31 20:24 ` Oliver Hartkopp
2015-03-30 12:33 ` Sergei Shtylyov
2015-03-30 15:49 ` Oliver Hartkopp
2015-03-30 17:14 ` Sergei Shtylyov
2015-03-30 17:25 ` Oliver Hartkopp
2015-03-29 18:09 ` [PATCH RFC v2 2/2] can: introduce new raw socket option to join the given " Oliver Hartkopp
2015-03-31 12:36 ` Marc Kleine-Budde
2015-03-31 20:30 ` 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=55192280.8090505@pengutronix.de \
--to=mkl@pengutronix.de \
--cc=linux-can@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=socketcan@hartkopp.net \
/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).