From: John Kacur <jkacur@redhat.com>
To: Jack Winch <sunt.un.morcov@gmail.com>
Cc: Punit Agrawal <punitagrawal@gmail.com>,
Pierre FICHEUX <pierre.ficheux@smile.fr>,
Sebastian Andrzej Siewior <bigeasy@linutronix.de>,
Clark Williams <williams@redhat.com>,
linux-rt-users <linux-rt-users@vger.kernel.org>,
Thomas Gleixner <tglx@linutronix.de>
Subject: Re: Strange problem with PREEMPT_RT
Date: Mon, 4 Oct 2021 08:54:36 -0400 (EDT) [thread overview]
Message-ID: <a37b2bd4-e141-675c-cb4a-164da3bc3358@redhat.com> (raw)
In-Reply-To: <CAFhCfDa5TQaEO_ZZwa0Y4v2Uy-B6=9B767gWw3z036bxz6Wsbw@mail.gmail.com>
On Sun, 3 Oct 2021, Jack Winch wrote:
> Punit Agrawal <punitagrawal@gmail.com> writes:
>
> > > If I remove this default we're going to get a slew of reports from people
> > > using cyclictest wondering why they aren't getting good realtime
> > > performance.
> >
> > Perhaps, this is a change best done with a major version bump. Not that
> > it'll stop users queries completely but hopefully more people will pay
> > attention to the changelog.
>
> Regrettably, I know quite a few RT Linux users who are neither party
> to this mailing list (due to company IT policy), nor do they pay
> attention to the changelog. Even less read the source code of the
> rt-tests suite of tools.
>
> Regardless of these sorrowful facts, as this is such a fundamental
> matter, perhaps it would be useful to highlight this behaviour of
> cyclictest in the tool's documentation - specifically the program's
> help output, manual page, and related content on the RT Linux wiki. I
> see additional information going into the first two forms of
> documentation as a required step. However, I believe that adding
> information on this behaviour to the relevant pages of the RT Linux
> wiki would also be greatly beneficial. This is because many
> developers who are new to RT Linux development, in my experience, tend
> to make use of the wiki to 'orientate' themselves when first starting
> out, etc, and the omission of information regarding this behaviour
> could lead to wrong assessments and conclusions being made when using
> this tool.
>
> Jack
>
Don't worry, I try to keep the help and man pages up-to-date so you don't
need to read change logs. If you see any problems with help / man pages
either report that to the list and cc me, or send me a patch.
Thanks
John Kacur
next prev parent reply other threads:[~2021-10-04 12:54 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-09-29 16:40 Strange problem with PREEMPT_RT Pierre FICHEUX
2021-09-30 0:13 ` Punit Agrawal
2021-09-30 8:21 ` Pierre FICHEUX
2021-09-30 13:17 ` Luis Goncalves
2021-09-30 13:18 ` Sebastian Andrzej Siewior
2021-09-30 13:23 ` Sebastian Andrzej Siewior
2021-09-30 13:26 ` Pierre FICHEUX
2021-09-30 13:51 ` Sebastian Andrzej Siewior
2021-09-30 14:31 ` Pierre FICHEUX
2021-09-30 23:40 ` Punit Agrawal
2021-10-03 11:11 ` Jack Winch
2021-10-04 12:54 ` John Kacur [this message]
2021-10-18 9:12 ` Sebastian Andrzej Siewior
2021-09-30 13:41 ` John Ogness
2021-09-30 14:25 ` John Kacur
2021-09-30 15:02 ` John Ogness
2021-09-30 15:49 ` Sebastian Andrzej Siewior
2021-09-30 16:16 ` John Kacur
2021-09-30 23:22 ` Punit Agrawal
2021-09-30 14:59 ` John Kacur
2021-09-30 23:01 ` Punit Agrawal
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=a37b2bd4-e141-675c-cb4a-164da3bc3358@redhat.com \
--to=jkacur@redhat.com \
--cc=bigeasy@linutronix.de \
--cc=linux-rt-users@vger.kernel.org \
--cc=pierre.ficheux@smile.fr \
--cc=punitagrawal@gmail.com \
--cc=sunt.un.morcov@gmail.com \
--cc=tglx@linutronix.de \
--cc=williams@redhat.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox