From: Peter Zijlstra <peterz@infradead.org>
To: Tejun Heo <tj@kernel.org>
Cc: Zefan Li <lizefan@huawei.com>,
Mike Galbraith <umgwanakikbuti@gmail.com>,
Ingo Molnar <mingo@kernel.org>,
LKML <linux-kernel@vger.kernel.org>,
Cgroups <cgroups@vger.kernel.org>
Subject: Re: [PATCH] sched: Relax a restriction in sched_rt_can_attach()
Date: Tue, 5 May 2015 21:00:57 +0200 [thread overview]
Message-ID: <20150505190057.GR23123@twins.programming.kicks-ass.net> (raw)
In-Reply-To: <20150505163112.GU1971@htj.duckdns.org>
On Tue, May 05, 2015 at 12:31:12PM -0400, Tejun Heo wrote:
>
> What I don't want to happen is controllers failing migrations
> willy-nilly for random reasons leaving users baffled, which we've
> actually been doing unfortunately. Maybe we need to deal with this
> fixed resource arbitration as a separate class and allow them to fail
> migration w/ -EBUSY.
Ah, _that_ was the problem.
Which is something created by this co-mounting of controllers.
You could of course store the ss-id of the failing operation in
task_struct and have a file reporting the name of the ss-id.
That way, there is a simple way to find out which controller failed the
migrate.
next prev parent reply other threads:[~2015-05-05 19:01 UTC|newest]
Thread overview: 43+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-05-04 0:54 [PATCH] sched: Relax a restriction in sched_rt_can_attach() Zefan Li
2015-05-04 0:54 ` Zefan Li
2015-05-04 3:13 ` Mike Galbraith
2015-05-04 3:13 ` Mike Galbraith
2015-05-04 4:39 ` Zefan Li
2015-05-04 4:39 ` Zefan Li
2015-05-04 5:10 ` Mike Galbraith
2015-05-04 5:10 ` Mike Galbraith
2015-05-04 5:39 ` Mike Galbraith
2015-05-04 5:39 ` Mike Galbraith
2015-05-04 9:11 ` Zefan Li
2015-05-04 9:11 ` Zefan Li
2015-05-04 12:08 ` Mike Galbraith
2015-05-04 12:08 ` Mike Galbraith
2015-05-04 12:37 ` Peter Zijlstra
2015-05-04 12:37 ` Peter Zijlstra
2015-05-04 14:09 ` Mike Galbraith
2015-05-05 3:46 ` Zefan Li
2015-05-05 3:46 ` Zefan Li
2015-05-05 6:02 ` Mike Galbraith
2015-05-05 6:02 ` Mike Galbraith
2015-05-05 3:54 ` Zefan Li
2015-05-05 3:54 ` Zefan Li
2015-05-05 14:10 ` Peter Zijlstra
2015-05-05 14:18 ` Tejun Heo
2015-05-05 15:19 ` Peter Zijlstra
2015-05-05 16:31 ` Tejun Heo
2015-05-05 19:00 ` Peter Zijlstra [this message]
2015-05-05 19:06 ` Tejun Heo
2015-05-05 19:06 ` Tejun Heo
2015-05-06 8:49 ` Peter Zijlstra
2015-05-06 8:49 ` Peter Zijlstra
2015-05-05 14:41 ` Tejun Heo
2015-05-05 15:11 ` Peter Zijlstra
2015-05-05 16:13 ` Tejun Heo
2015-05-05 16:50 ` Peter Zijlstra
2015-05-05 18:29 ` Thomas Gleixner
2015-05-05 19:00 ` Tejun Heo
2015-05-05 19:00 ` Tejun Heo
2015-05-06 9:12 ` Thomas Gleixner
2015-05-05 18:31 ` Tejun Heo
2015-05-05 14:09 ` Tejun Heo
2015-05-05 14:09 ` Tejun Heo
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=20150505190057.GR23123@twins.programming.kicks-ass.net \
--to=peterz@infradead.org \
--cc=cgroups@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lizefan@huawei.com \
--cc=mingo@kernel.org \
--cc=tj@kernel.org \
--cc=umgwanakikbuti@gmail.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.