All of lore.kernel.org
 help / color / mirror / Atom feed
From: Daniel Santos <daniel.santos@pobox.com>
To: linux-can <linux-can@vger.kernel.org>
Subject: Framework for hardware filter support?
Date: Sat, 10 Feb 2018 20:38:15 -0600	[thread overview]
Message-ID: <98bcd448-4d2a-bf2f-ae5a-4db7f1eac896@pobox.com> (raw)

Hello.  I'm doing a project where hardware filters will pretty much be
required unless we change the hardware.  I can just hack up the mcp251x
driver and add some sysfs nodes to modify the filters, but it would be
much nicer to implement using some type of standard framework that I
could submit back upstream.

My current project uses an MCP2515 (with only two rx buffers) connected
via an MCP2210 USB-to-SPI bridge and that introduces a lot of latency
and interrupts may not be serviced for as much as 20-30 ms and w/o
hardware filters, we'll be missing a lot of messages we want to sniff.

I've read some of the arguments against it, such is it being a
multi-user environment.  To me that just means that hardware filters
should be configured at the interface level and not at the socket level.

So is there no such framework already in place?  If not, where would be
the most logical place to add it? netfilter in the kernel and iproute2
in userland?

Thanks,
Daniel



             reply	other threads:[~2018-02-11  2:38 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-02-11  2:38 Daniel Santos [this message]
2018-02-11 12:32 ` Framework for hardware filter support? Oliver Hartkopp
2018-02-11 22:33   ` Daniel Santos
2018-02-13 19:42     ` Kurt Van Dijck
2018-02-13 20:44       ` Oliver Hartkopp
2018-02-14 22:40       ` Daniel Santos
2018-02-15 23:03         ` Kurt Van Dijck

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=98bcd448-4d2a-bf2f-ae5a-4db7f1eac896@pobox.com \
    --to=daniel.santos@pobox.com \
    --cc=linux-can@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.