From: Christopher Lameter <cl@linux.com>
To: Peter Zijlstra <peterz@infradead.org>
Cc: Marcelo Tosatti <mtosatti@redhat.com>,
linux-kernel@vger.kernel.org,
Frederic Weisbecker <fweisbec@gmail.com>,
Chris Friesen <chris.friesen@windriver.com>,
Thomas Gleixner <tglx@linutronix.de>,
Andrew Morton <akpm@linux-foundation.org>,
Jim Somerville <Jim.Somerville@windriver.com>
Subject: Re: [patch 3/3] isolcpus: undeprecate on documentation
Date: Sat, 4 Apr 2020 23:05:52 +0000 (UTC) [thread overview]
Message-ID: <alpine.DEB.2.21.2004042302080.1722@www.lameter.com> (raw)
In-Reply-To: <20200331155708.GU20730@hirez.programming.kicks-ass.net>
On Tue, 31 Mar 2020, Peter Zijlstra wrote:
> > Why do you dislike it? What you think would be a decent approach?
>
> Try and reconfigure it after boot.
Not really a problem since this is not the only issue that requires a
reboot.
You have to reboot most of the time if you change applications on a HPC
machine. After all you cannot reliably change the available set of huge
pages after boot. So you have to reboot anyways if you want some cores to
do different things.
And then the machines performance goes down over time due to
memory fragmentation. So you better reboot frequently.
Thus reboot, reboot, reboot. We have become like Windows 95 ...
next prev parent reply other threads:[~2020-04-04 23:05 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-03-28 15:21 [patch 0/3] affine kernel threads to specified cpumask (v3) Marcelo Tosatti
2020-03-28 15:21 ` [patch 1/3] kthread: switch to cpu_possible_mask Marcelo Tosatti
2020-03-28 15:21 ` [patch 2/3] isolcpus: affine kernel threads to specified cpumask Marcelo Tosatti
2020-03-31 0:57 ` Frederic Weisbecker
2020-03-31 11:50 ` Marcelo Tosatti
2020-03-31 13:36 ` Frederic Weisbecker
2020-03-28 15:21 ` [patch 3/3] isolcpus: undeprecate on documentation Marcelo Tosatti
2020-03-31 15:22 ` Peter Zijlstra
2020-03-31 15:41 ` Marcelo Tosatti
2020-03-31 15:57 ` Peter Zijlstra
2020-04-04 23:05 ` Christopher Lameter [this message]
2020-03-31 15:43 ` Frederic Weisbecker
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=alpine.DEB.2.21.2004042302080.1722@www.lameter.com \
--to=cl@linux.com \
--cc=Jim.Somerville@windriver.com \
--cc=akpm@linux-foundation.org \
--cc=chris.friesen@windriver.com \
--cc=fweisbec@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mtosatti@redhat.com \
--cc=peterz@infradead.org \
--cc=tglx@linutronix.de \
/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.