From: Borislav Petkov <bp@alien8.de>
To: "Paul E. McKenney" <paulmck@kernel.org>
Cc: linux-kernel@vger.kernel.org, linux-tip-commits@vger.kernel.org,
x86 <x86@kernel.org>
Subject: Re: [tip: core/rcu] rcu: Enable tick for nohz_full CPUs slow to provide expedited QS
Date: Sat, 25 Jan 2020 21:19:05 +0100 [thread overview]
Message-ID: <20200125201904.GB4369@zn.tnic> (raw)
In-Reply-To: <20200125194846.GF2935@paulmck-ThinkPad-P72>
On Sat, Jan 25, 2020 at 11:48:46AM -0800, Paul E. McKenney wrote:
> My guess is "no" because the real-time application would not yet be
> running during boot. On the other hand, if this issue is due not so much
> to boot, but to (say) expensive filesystem operations on large systems,
> that might be a different story.
Possible - that warn happened around a btrfs init-something.
> Except that I would have hard questions to ask of someone doing expensive
> filesystem operations while their deep-sub-millisecond real-time
> application was running. So even then, I doubt that they would care.
>
> Again, if I am wrong about this, this would be an excellent time for
> them to let me know.
I can see the hint there. :-)
> In the meantime, one question... Are you testing for realtime suitability
> on your big box? If so, to what extent?
Nah, just boot-testing tip/master before the merge window opens. Got a
couple of boxes on which I throw tip/master on from time to time and see
what breaks. I have caught a number of issues in past years, so it is a
useful exercise.
> Aside from habitually failing to trim emails, which of these was I
> violating? ;-)
That's my mail signature. In the hope that people see that doc and stop
doing the same annoying things on LKML, it gets pasted in every mail of
mine. I didn't mean you or your mail.
:-)
--
Regards/Gruss,
Boris.
https://people.kernel.org/tglx/notes-about-netiquette
next prev parent reply other threads:[~2020-01-25 20:19 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-01-25 10:42 tip-bot2 for Paul E. McKenney
2020-01-25 13:14 ` Borislav Petkov
2020-01-25 16:10 ` Paul E. McKenney
2020-01-25 17:54 ` Borislav Petkov
2020-01-25 19:48 ` Paul E. McKenney
2020-01-25 20:08 ` Paul E. McKenney
2020-01-25 20:23 ` Borislav Petkov
2020-01-25 20:19 ` Borislav Petkov [this message]
2020-01-26 1:43 ` Paul E. McKenney
2020-01-26 11:25 ` Borislav Petkov
2020-01-26 15:28 ` Paul E. McKenney
2020-01-26 17:19 ` Borislav Petkov
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=20200125201904.GB4369@zn.tnic \
--to=bp@alien8.de \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-tip-commits@vger.kernel.org \
--cc=paulmck@kernel.org \
--cc=x86@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®