From: Oliver Hartkopp <socketcan@hartkopp.net>
To: Holger Schurig <holgerschurig@gmail.com>
Cc: "list@hauke-m.de:NETWORKING DRIVERS" <netdev@vger.kernel.org>,
therbert.google.com@vger.kernel.org,
"linux-can@vger.kernel.org" <linux-can@vger.kernel.org>,
sunil.kovvuri@gmail.com, jonathon.reinhart@gmail.com
Subject: Re: Fighting out-of-order reception with RPS?
Date: Thu, 09 Jul 2015 10:48:22 +0200 [thread overview]
Message-ID: <559E3556.3050803@hartkopp.net> (raw)
In-Reply-To: <CAOpc7mEEOHr=QWazthRuWuoOvr_C_4O1hO8bP-N36tLT+RBifw@mail.gmail.com>
On 09.07.2015 08:34, Holger Schurig wrote:
>> and has to be done by hand depending on where the CAN interfaces
>> are attached to the system.
>
> No ... udev rules rock! :-)
>
Yeah. But it can not be the approach to fix a known problem in the kernel by
urging people to make workarounds in userspace. For my testing I did it by
hand. But in real life the kernel has to do 'the right thing' by having wise
defaults without interaction.
Regards,
Oliver
prev parent reply other threads:[~2015-07-09 8:48 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-07-08 17:49 Fighting out-of-order reception with RPS? Oliver Hartkopp
2015-07-08 21:17 ` Tom Herbert
2015-07-09 5:55 ` Oliver Hartkopp
2015-07-10 2:48 ` Tom Herbert
2015-07-10 20:36 ` Oliver Hartkopp
2015-07-11 4:35 ` Eric Dumazet
2015-07-12 19:15 ` Oliver Hartkopp
2015-07-13 3:22 ` David Miller
2015-07-13 4:57 ` Eric Dumazet
2015-07-14 17:09 ` Oliver Hartkopp
2015-07-14 18:02 ` Tom Herbert
2015-07-14 19:03 ` David Miller
2015-07-14 19:05 ` Oliver Hartkopp
2015-07-13 19:08 ` Tom Herbert
2015-07-09 6:34 ` Holger Schurig
2015-07-09 8:48 ` 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=559E3556.3050803@hartkopp.net \
--to=socketcan@hartkopp.net \
--cc=holgerschurig@gmail.com \
--cc=jonathon.reinhart@gmail.com \
--cc=linux-can@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=sunil.kovvuri@gmail.com \
--cc=therbert.google.com@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.