From: Gene Heskett <gheskett@shentel.net>
To: linux-rt-users@vger.kernel.org
Subject: Re: SCHED_DEADLINE as user
Date: Thu, 23 Aug 2018 14:07:35 -0400 [thread overview]
Message-ID: <201808231407.35449.gheskett@shentel.net> (raw)
In-Reply-To: <5B7EDA65.7000906@windriver.com>
On Thursday 23 August 2018 12:01:41 Chris Friesen wrote:
> On 08/23/2018 07:45 AM, Gene Heskett wrote:
> > LinuxCNC is also run as a common user, never as root. Thats my
> > $0.02 from a users viewpoint.
>
> Given that these are special-purpose machines, can I ask why you
> wouldn't run as root if it gave better performance?
>
> Chris
Its a rather bad habit, and if I get used to doing it on this machine, I
might do it on one of the metal carvers, which has a tendency to mess
with the user perms. Root or known user is all the same to lcnc AFAIK.
I have done it 3 or 4 times, but there is no detectable diff in
performance. But sometime in the last few years it has now been trained
to refuse to run as root.
The kernel argument isolcpus= comes in handy occasionally on really old
but still multicore hdwe but has had little or no effect since about
kernel 3.4.0 built for SMP and PREEMPT. We don't use more than 2GB of
d-ram for the same reason, the patches to give a 4GB capable address are
also a performance penalty.
Currently running
Linux GO704 3.4-9-rtai-686-pae #1 SMP PREEMPT Debian 3.4.55-4linuxcnc
i686 GNU/Linux, a 32 bit build because its faster at a context switch
than the larger stack image the 64 bit build uses.
This machine, my "doitall" machine doesn't drive any of that sort of
hardware, and is currently running:3.16.0-0.bpo.4-amd64 #1 SMP Debian
3.16.39-1+deb8u1~bpo70+1 (2017-02-24) x86_64 GNU/Linux which will run
the simulator so I can write cgode from a comfy chair. Then export it
with sshfs to the machine that will actually make the swarf, aka
metallic sawdust.
Thanks Chris.
--
Cheers, Gene Heskett
--
"There are four boxes to be used in defense of liberty:
soap, ballot, jury, and ammo. Please use in that order."
-Ed Howdershelt (Author)
Genes Web page <http://geneslinuxbox.net:6309/gene>
prev parent reply other threads:[~2018-08-23 21:39 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-08-15 6:08 SCHED_DEADLINE as user Tim Blechmann
2018-08-15 8:21 ` Daniel Bristot de Oliveira
2018-08-17 9:51 ` Juri Lelli
2018-08-17 10:08 ` Tim Blechmann
2018-08-17 10:28 ` Juri Lelli
[not found] ` <513fd544-bc51-7ea6-8b94-983d28922a66@klingt.org>
2018-08-20 8:54 ` Juri Lelli
2018-08-20 11:54 ` Tim Blechmann
2018-08-20 12:38 ` Daniel Bristot de Oliveira
2018-08-20 13:55 ` Tim Blechmann
[not found] ` <e207a65d-b1af-3fb1-8802-d1c05c0a9118@bristot.me>
[not found] ` <05fbd5a4-f354-e084-cf40-8488548d7cb1@klingt.org>
2018-08-21 6:55 ` Tommaso Cucinotta
2018-08-21 7:38 ` Juri Lelli
2018-08-22 8:49 ` Juri Lelli
2018-08-21 7:17 ` Tommaso Cucinotta
2018-08-21 7:59 ` Tim Blechmann
2018-08-23 9:56 ` luca abeni
2018-08-23 10:23 ` Juri Lelli
2018-08-23 10:43 ` luca abeni
2018-08-23 12:37 ` Juri Lelli
2018-08-23 12:58 ` luca abeni
2018-08-23 13:00 ` luca abeni
2018-08-23 13:09 ` Juri Lelli
2018-08-23 13:30 ` luca abeni
2018-08-23 13:45 ` Gene Heskett
2018-08-23 16:01 ` Chris Friesen
2018-08-23 18:07 ` Gene Heskett [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=201808231407.35449.gheskett@shentel.net \
--to=gheskett@shentel.net \
--cc=linux-rt-users@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.