linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Juri Lelli <juri.lelli@arm.com>
To: Daniel Bristot de Oliveira <daolivei@redhat.com>
Cc: linux-kernel@vger.kernel.org, Rik van Riel <riel@redhat.com>,
	"Luis Claudio R. Goncalves" <lgoncalv@redhat.com>,
	Tejun Heo <tj@kernel.org>, Li Zefan <lizefan@huawei.com>,
	Johannes Weiner <hannes@cmpxchg.org>,
	cgroups@vger.kernel.org
Subject: Re: [PATCH] cgroup: disable irqs while holding css_set_lock
Date: Tue, 7 Jun 2016 17:11:34 +0100	[thread overview]
Message-ID: <20160607161134.GU9340@e106622-lin> (raw)
In-Reply-To: <494c1f85-bbab-99f1-4095-914aaebdd708@redhat.com>

On 07/06/16 12:26, Daniel Bristot de Oliveira wrote:
> Ciao Juri,
> 
> On 06/07/2016 10:30 AM, Juri Lelli wrote:
> > So, this and the partitioned one could actually overlap, since we don't
> > set cpu_exclusive. Is that right?
> > 
> > I guess affinity mask of both m processes gets set correclty, but I'm
> > not sure if we are missing one check in the admission control. Can you
> > actually create two overlapping sets and get DEADLINE tasks running in
> > them? For example, what happens if partitioned is [4] and clustered is
> > [4-7]? Does setattr() fail?
> 
> That is what I was trying to understand/break. Fortunately, I still
> can't break it! bravo! :-)
> 
> In the test you mentioned the task in the "clustered" fails to
> sched_setattr().
> 
> Test output example:
> + '[' '!' -d partitioned ']'
> + mkdir partitioned
> + echo 4
> + echo 0
> + echo 0
> + echo 1155
> + cat /proc/self/cpuset
> /partitioned
> + /root/m
> main thread [1162]
> deadline thread started [1164]

Mmm. The other one is good, but this one looks still suspect to me. We
shouldn't have created a new root domain at this point (since
cpu_exclusive is not set), so we shouldn't be able to admit DEADLINE
tasks with a smaller affinity mask than the full root domain mask (which
should still be 0-7 at this point), if I'm interpreting your script correctly
and I'm not wrong about root domains stuff.

Unfortunately I'm not able to test this myself right now. Hopefully next
week.

Thanks a lot for testing, though!

Best,

- Juri

> + '[' '!' -d clustered ']'
> + mkdir clustered
> + echo 4-7
> + echo 0
> + echo 0
> + echo 1
> + echo 1155
> + cat /proc/self/cpuset
> + /root/m
> /clustered
> + /root/m
> main thread [1166]
> sched_setattr: Operation not permitted
> 
> I will let you know if I find something odd.
> 
> -- Daniel
> 

  reply	other threads:[~2016-06-07 16:11 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-06-06 22:24 [PATCH] cgroup: disable irqs while holding css_set_lock Daniel Bristot de Oliveira
2016-06-07 10:14 ` Juri Lelli
2016-06-07 12:39   ` Daniel Bristot de Oliveira
2016-06-07 13:30     ` Juri Lelli
2016-06-07 15:26       ` Daniel Bristot de Oliveira
2016-06-07 16:11         ` Juri Lelli [this message]
2016-06-07 15:13 ` Daniel Bristot de Oliveira

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=20160607161134.GU9340@e106622-lin \
    --to=juri.lelli@arm.com \
    --cc=cgroups@vger.kernel.org \
    --cc=daolivei@redhat.com \
    --cc=hannes@cmpxchg.org \
    --cc=lgoncalv@redhat.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=lizefan@huawei.com \
    --cc=riel@redhat.com \
    --cc=tj@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).