From: Oliver Hartkopp <socketcan@hartkopp.net>
To: Prabhakar Lad <prabhakar.csengg@gmail.com>
Cc: "linux-can@vger.kernel.org" <linux-can@vger.kernel.org>
Subject: Re: [RFC] sched policies for candump
Date: Thu, 18 Dec 2014 14:51:11 +0100 [thread overview]
Message-ID: <5492DBCF.2010500@hartkopp.net> (raw)
In-Reply-To: <CA+V-a8uBmfbzAD1eXoejs4H-JQwXWbY+2b0n0fauy54P=BE9sg@mail.gmail.com>
On 18.12.2014 13:33, Prabhakar Lad wrote:
>> Is this still needed / valuable?
>>
> If I remember correctly we agreed upon using chrt/nice to achieve this.
>
> But I still feel having an option in the tool itself would be better
> choice as some
> of the novice users might not be aware of chrt/nice.
>
Ah - now I remember myself.
The point was that you then become in charge to put this into all relevant
tools - which is probably not what you want.
So increase the awareness for novice users to use chrt/nice looks like the
better option ;-)
Best regards,
Oliver
prev parent reply other threads:[~2014-12-18 13:51 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-07-23 14:48 C_CAN: can frame drops Ssagarr Patil
2014-07-23 16:04 ` Oliver Hartkopp
2014-07-23 16:33 ` Ssagarr Patil
2014-07-24 7:40 ` Ssagarr Patil
2014-07-24 18:09 ` Oliver Hartkopp
2014-07-25 8:20 ` Ssagarr Patil
2014-07-25 7:17 ` Marc Kleine-Budde
2014-07-25 8:13 ` Ssagarr Patil
2014-07-25 8:16 ` Marc Kleine-Budde
2014-07-25 8:22 ` Ssagarr Patil
2014-07-25 8:27 ` Marc Kleine-Budde
2014-07-25 8:35 ` Ssagarr Patil
2014-07-25 8:48 ` Marc Kleine-Budde
2014-07-25 9:47 ` Ssagarr Patil
2014-07-25 10:10 ` Marc Kleine-Budde
2014-07-25 11:22 ` Ssagarr Patil
2014-07-25 10:43 ` Oliver Hartkopp
2014-07-25 11:24 ` Ssagarr Patil
2014-07-30 11:28 ` Prabhakar Lad
2014-07-30 16:17 ` Oliver Hartkopp
2014-07-31 12:41 ` Ssagarr Patil
2014-07-31 12:42 ` Marc Kleine-Budde
2014-07-31 14:11 ` Oliver Hartkopp
2014-07-31 14:19 ` Prabhakar Lad
2014-12-18 9:41 ` [RFC] sched policies for candump Oliver Hartkopp
2014-12-18 12:33 ` Prabhakar Lad
2014-12-18 13:51 ` 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=5492DBCF.2010500@hartkopp.net \
--to=socketcan@hartkopp.net \
--cc=linux-can@vger.kernel.org \
--cc=prabhakar.csengg@gmail.com \
/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.