From: Kevin Puetz <puetzk@puetzk.org>
To: linux-kernel@vger.kernel.org
Subject: RE: Industry db benchmark result on recent 2.6 kernels
Date: Sun, 03 Apr 2005 20:40:12 -0500 [thread overview]
Message-ID: <d2q5ql$9j3$1@sea.gmane.org> (raw)
In-Reply-To: Pine.LNX.4.58.0504011447580.4774@ppc970.osdl.org
Linus Torvalds wrote:
>
>
> On Fri, 1 Apr 2005, Chen, Kenneth W wrote:
>>
>> Paul, you definitely want to check this out on your large numa box. I
>> booted a kernel with this patch on a 32-way numa box and it took a long
>> .... time to produce the cost matrix.
>
> Is there anything fundamentally wrong with the notion of just initializing
> the cost matrix to something that isn't completely wrong at bootup, and
> just lettign user space fill it in?
Wouldn't getting rescheduled (and thus having another program trash the
cache on you) really mess up the data collection though? I suppose by
spawning off threads, each with a fixed affinity and SCHED_FIFO one could
hang onto the CPU to collect the data. But then it's not (a lot) different
than doing it in-kernel.
> Then you couple that with a program that can do so automatically (ie
> move the in-kernel heuristics into user-land), and something that can
> re-load it on demand.
This part seems sensible though :-)
> Voila - you have something potentially expensive that you run once, and
> then you have a matrix that can be edited by the sysadmin later and just
> re-loaded at each boot.. That sounds pretty optimal, especially in the
> sense that it allows the sysadmin to tweak things depending on the use of
> the box is he really wants to.
>
> Hmm? Or am I just totally on crack?
>
> Linus
next prev parent reply other threads:[~2005-04-04 1:40 UTC|newest]
Thread overview: 41+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-03-28 19:33 Industry db benchmark result on recent 2.6 kernels Chen, Kenneth W
2005-03-28 19:50 ` Dave Hansen
2005-03-28 20:01 ` Chen, Kenneth W
2005-03-30 0:00 ` Linus Torvalds
2005-03-30 0:22 ` Chen, Kenneth W
2005-03-30 0:46 ` Chen, Kenneth W
2005-03-30 0:57 ` Linus Torvalds
2005-03-30 1:31 ` Nick Piggin
2005-03-30 1:38 ` Chen, Kenneth W
2005-03-30 1:56 ` Nick Piggin
2005-03-31 14:14 ` Ingo Molnar
2005-03-31 19:53 ` Chen, Kenneth W
2005-03-31 20:05 ` Linus Torvalds
2005-03-31 20:08 ` Linus Torvalds
2005-03-31 22:14 ` Chen, Kenneth W
2005-03-31 23:35 ` Nick Piggin
2005-04-01 6:05 ` Paul Jackson
2005-04-01 6:34 ` Nick Piggin
2005-04-01 7:19 ` Paul Jackson
2005-04-01 6:46 ` Ingo Molnar
2005-04-01 22:32 ` Chen, Kenneth W
2005-04-01 22:51 ` Linus Torvalds
2005-04-02 2:19 ` Nick Piggin
2005-04-04 1:40 ` Kevin Puetz [this message]
2005-04-02 1:44 ` Paul Jackson
2005-04-02 2:05 ` Chen, Kenneth W
2005-04-02 2:38 ` Paul Jackson
2005-04-03 6:36 ` David Lang
2005-04-03 6:53 ` Andreas Dilger
2005-04-03 7:23 ` David Lang
2005-04-03 7:38 ` Nick Piggin
2005-04-01 6:59 ` Ingo Molnar
2005-04-01 9:29 ` Paul Jackson
2005-04-01 10:34 ` Ingo Molnar
2005-04-01 14:39 ` Paul Jackson
2005-04-01 4:52 ` Ingo Molnar
2005-04-01 5:14 ` Chen, Kenneth W
2005-04-01 22:51 ` Chen, Kenneth W
-- strict thread matches above, loose matches on Subject: below --
2005-04-01 16:34 Manfred Spraul
2005-04-02 1:00 Chen, Kenneth W
2005-04-02 2:12 ` Nick Piggin
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='d2q5ql$9j3$1@sea.gmane.org' \
--to=puetzk@puetzk.org \
--cc=linux-kernel@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.