From: Michael wang <wangyun@linux.vnet.ibm.com>
To: Peter Zijlstra <peterz@infradead.org>, Rik van Riel <riel@redhat.com>
Cc: LKML <linux-kernel@vger.kernel.org>,
Ingo Molnar <mingo@kernel.org>, Mike Galbraith <efault@gmx.de>,
Alex Shi <alex.shi@linaro.org>, Paul Turner <pjt@google.com>,
Mel Gorman <mgorman@suse.de>,
Daniel Lezcano <daniel.lezcano@linaro.org>
Subject: Re: [ISSUE] sched/cgroup: Does cpu-cgroup still works fine nowadays?
Date: Wed, 14 May 2014 11:27:36 +0800 [thread overview]
Message-ID: <5372E2A8.6070903@linux.vnet.ibm.com> (raw)
In-Reply-To: <20140513142328.GE2485@laptop.programming.kicks-ass.net>
On 05/13/2014 10:23 PM, Peter Zijlstra wrote:
[snip]
>
> The point remains though, don't use massive and awkward software stacks
> that are impossible to operate.
>
> I you want to investigate !spinners, replace the ABC with slightly more
> complex loads like: https://lkml.org/lkml/2012/6/18/212
That's what we need, may be a little reform to enable multi-threads, or
may be add some locks... anyway, will redo the test and see what we
could found :)
Regards,
Michael Wang
> --
> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at http://www.tux.org/lkml/
>
next prev parent reply other threads:[~2014-05-14 3:27 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-05-13 3:34 [ISSUE] sched/cgroup: Does cpu-cgroup still works fine nowadays? Michael wang
2014-05-13 9:47 ` Peter Zijlstra
2014-05-13 13:36 ` Rik van Riel
2014-05-13 14:23 ` Peter Zijlstra
2014-05-14 3:27 ` Michael wang [this message]
2014-05-14 7:36 ` Michael wang
2014-05-14 9:44 ` Peter Zijlstra
2014-05-15 3:46 ` Michael wang
2014-05-15 8:35 ` Peter Zijlstra
2014-05-15 8:46 ` Michael wang
2014-05-15 9:06 ` Peter Zijlstra
2014-05-15 9:35 ` Michael wang
2014-05-15 11:57 ` Peter Zijlstra
2014-05-16 2:23 ` Michael wang
2014-05-16 2:51 ` Mike Galbraith
2014-05-16 4:24 ` Michael wang
2014-05-16 7:54 ` Peter Zijlstra
2014-05-16 8:15 ` Michael wang
2014-06-10 8:56 ` Michael wang
2014-06-10 12:12 ` Peter Zijlstra
2014-06-11 6:13 ` Michael wang
2014-06-11 8:24 ` Peter Zijlstra
2014-06-11 9:18 ` Michael wang
2014-06-23 9:42 ` Peter Zijlstra
2014-06-24 3:10 ` Michael wang
2014-05-16 7:48 ` Peter Zijlstra
2014-05-14 3:21 ` Michael wang
2014-05-14 3:16 ` Michael wang
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=5372E2A8.6070903@linux.vnet.ibm.com \
--to=wangyun@linux.vnet.ibm.com \
--cc=alex.shi@linaro.org \
--cc=daniel.lezcano@linaro.org \
--cc=efault@gmx.de \
--cc=linux-kernel@vger.kernel.org \
--cc=mgorman@suse.de \
--cc=mingo@kernel.org \
--cc=peterz@infradead.org \
--cc=pjt@google.com \
--cc=riel@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 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.