From: Marc Kleine-Budde <mkl@pengutronix.de>
To: Oliver Hartkopp <socketcan@hartkopp.net>, linux-can@vger.kernel.org
Cc: netdev@vger.kernel.org, sergei.shtylyov@cogentembedded.com
Subject: Re: [RFC PATCH v3 1/2] can: fix multiple delivery of a single CAN frame for overlapping CAN filters
Date: Wed, 01 Apr 2015 11:07:33 +0200 [thread overview]
Message-ID: <551BB555.7030808@pengutronix.de> (raw)
In-Reply-To: <1427867429-3909-2-git-send-email-socketcan@hartkopp.net>
[-- Attachment #1: Type: text/plain, Size: 1667 bytes --]
On 04/01/2015 07:50 AM, 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.
>
> 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 raw_rcv() 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>
> ---
> net/can/raw.c | 21 +++++++++++++++++++++
> 1 file changed, 21 insertions(+)
>
> diff --git a/net/can/raw.c b/net/can/raw.c
> index 00c13ef..8c75446 100644
> --- a/net/can/raw.c
> +++ b/net/can/raw.c
> @@ -74,6 +74,11 @@ MODULE_ALIAS("can-proto-1");
> * storing the single filter in dfilter, to avoid using dynamic memory.
> */
>
> +struct uniqframe {
> + const struct sk_buff *skb;
> + ktime_t tstamp;
> +};
Nitpick: as ktime_t is always a 64 bit value, I think putting it first
might provide better alignment.
No need to repost, I'll change this while applying, if you're okay with
this.
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-04-01 9:07 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-04-01 5:50 [RFC PATCH v3 0/2] can: join filters with per-CPU variables Oliver Hartkopp
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 [this message]
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=551BB555.7030808@pengutronix.de \
--to=mkl@pengutronix.de \
--cc=linux-can@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=sergei.shtylyov@cogentembedded.com \
--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).