All of lore.kernel.org
 help / color / mirror / Atom feed
From: Oliver Hartkopp <socketcan@hartkopp.net>
To: Marc Kleine-Budde <mkl@pengutronix.de>, linux-can@vger.kernel.org
Cc: netdev@vger.kernel.org
Subject: Re: [PATCH RFC v2 2/2] can: introduce new raw socket option to join the given CAN filters
Date: Tue, 31 Mar 2015 22:30:09 +0200	[thread overview]
Message-ID: <551B03D1.2020801@hartkopp.net> (raw)
In-Reply-To: <551A94D0.1010608@pengutronix.de>

On 31.03.2015 14:36, Marc Kleine-Budde wrote:
> On 03/29/2015 08:09 PM, Oliver Hartkopp wrote:


>> @@ -128,10 +130,20 @@ static void raw_rcv(struct sk_buff *oskb, void *data)
>>   	/* 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)) {
>> +		if (ro->join_filters) {
>> +			this_cpu_inc(*ro->join_rx_count);
>> +			/* drop frame until all enabled filters matched */
>> +			if (*this_cpu_ptr(ro->join_rx_count) < ro->count)
>
> Can we be sure, that all skbs are processed on the same CPU? So that
> it's sufficient to just compare the "ro->join_rx_count" of this CPU with
> "ro->count" (or do we have to use join_rx_count of all CPUs?)
>

No, that's exactly the point that the single CAN frame skb is processed inside 
the softirq by one CPU. And we count only for this specific skb here.

The next frame which is processed in raw_rcv() might use another CPU while 
executing the NET_RX softirq.

>> +				return;
>> +		} else
>>   			return;
>
> nitpick: please use { } on both sides of the else.
>

fixed in v3

Regards,
Oliver



      reply	other threads:[~2015-03-31 20:30 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
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 [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=551B03D1.2020801@hartkopp.net \
    --to=socketcan@hartkopp.net \
    --cc=linux-can@vger.kernel.org \
    --cc=mkl@pengutronix.de \
    --cc=netdev@vger.kernel.org \
    /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.