From: Peter Zijlstra <peterz@infradead•org>
To: Nishanth Aravamudan <nacc@linux•vnet.ibm.com>
Cc: Boqun Feng <boqun.feng@linux•vnet.ibm.com>,
Srikar Dronamraju <srikar@linux•vnet.ibm.com>,
linux-kernel@vger•kernel.org, Ingo Molnar <mingo@redhat•com>,
Anton Blanchard <anton@samba•org>,
linuxppc-dev@lists•ozlabs.org,
Anshuman Khandual <khandual@linux•vnet.ibm.com>
Subject: Re: Topology updates and NUMA-level sched domains
Date: Fri, 10 Apr 2015 11:08:10 +0200 [thread overview]
Message-ID: <20150410090810.GW24151@twins.programming.kicks-ass.net> (raw)
In-Reply-To: <20150410083153.GQ27490@worktop.programming.kicks-ass.net>
On Fri, Apr 10, 2015 at 10:31:53AM +0200, Peter Zijlstra wrote:
> Please, step back, look at what you're doing and ask yourself, will any
> sane person want to use this? Can they use this?
>
> If so, start by describing the desired user semantics of this work.
> Don't start by cobbling kernel bits togerther until it stops crashing.
Also, please talk to your s390 folks. They've long since realized that
this doesn't work. They've just added big honking caches (their BOOK
stuff) and pretend the system is UMA.
next prev parent reply other threads:[~2015-04-10 9:08 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-04-06 21:45 Topology updates and NUMA-level sched domains Nishanth Aravamudan
2015-04-07 10:21 ` Peter Zijlstra
2015-04-07 17:14 ` Nishanth Aravamudan
2015-04-07 19:41 ` Peter Zijlstra
2015-04-08 10:32 ` Brice Goglin
2015-04-08 10:52 ` Peter Zijlstra
2015-04-09 22:40 ` Nishanth Aravamudan
2015-04-09 22:37 ` Nishanth Aravamudan
2015-04-09 22:29 ` Nishanth Aravamudan
2015-04-10 8:31 ` Peter Zijlstra
2015-04-10 9:08 ` Peter Zijlstra [this message]
2015-04-10 19:50 ` Nishanth Aravamudan
2015-04-10 20:30 ` Nishanth Aravamudan
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=20150410090810.GW24151@twins.programming.kicks-ass.net \
--to=peterz@infradead$(echo .)org \
--cc=anton@samba$(echo .)org \
--cc=boqun.feng@linux$(echo .)vnet.ibm.com \
--cc=khandual@linux$(echo .)vnet.ibm.com \
--cc=linux-kernel@vger$(echo .)kernel.org \
--cc=linuxppc-dev@lists$(echo .)ozlabs.org \
--cc=mingo@redhat$(echo .)com \
--cc=nacc@linux$(echo .)vnet.ibm.com \
--cc=srikar@linux$(echo .)vnet.ibm.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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