From: Juri Lelli <juri.lelli@gmail.com>
To: Kevin Burns <kevinpb@vt.edu>
Cc: linux-rt-users@vger.kernel.org
Subject: Re: set_schedattr + cpuset issue
Date: Thu, 10 Jul 2014 12:20:33 +0200 [thread overview]
Message-ID: <20140710122033.58bdd366fe3f869a71b1c05e@gmail.com> (raw)
In-Reply-To: <CAMLzMweCcxPBJExGsY-2oHK6sdF6EVgBsa1XVxQT0=kzNRZAJQ@mail.gmail.com>
Hi Kevin,
On Wed, 2 Jul 2014 17:08:47 -0400
Kevin Burns <kevinpb@vt.edu> wrote:
> Hello Mr. Lelli,
>
> I am a graduate student at Virginia Tech and am having an issue with
> sched_setattr.
>
> The folks over at at #linux-rt on irc.oftc.net suggested I bring the issue
> to your attention.
>
Sorry for the late reply, but I'm traveling in these days.
> Here's the issue:
>
> I am able to allocate a bandwidth with a ratio of .1 to two processes using
> the sched_setattr() system call.
>
> I then am able to add said tasks to a cpuset (with one physical processor)
> using cset.
>
> However, when I then try to update the runtime or period of either task,
> sched_setattr returns a -EBUSY error.
>
> Now, if I repeat the above experiment with just one task, I am able to
> update the runtime or period without issue. I ran trace-cmd and kernelshark
> to verify that the bandwidths were indeed being updated correctly. That and
> htop was reporting a higher percentage of CPUusage, which correlated to the
> ratios of my task's bandwidth.
>
> Any ideas as to why cpuset would cause this behaviour?
>
Could you create a script that I can use to run your setup and reproduce
the problem?
Thanks,
- Juri
> Thanks,
> -Kevin
next parent reply other threads:[~2014-07-10 10:20 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CAMLzMweCcxPBJExGsY-2oHK6sdF6EVgBsa1XVxQT0=kzNRZAJQ@mail.gmail.com>
2014-07-10 10:20 ` Juri Lelli [this message]
2014-08-28 21:07 ` set_schedattr + cpuset issue Vincent Legout
2014-09-02 10:36 ` Juri Lelli
2014-09-02 14:16 ` Vincent Legout
2014-09-03 10:00 ` Daniel Wagner
2014-09-03 13:06 ` Daniel Wagner
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=20140710122033.58bdd366fe3f869a71b1c05e@gmail.com \
--to=juri.lelli@gmail.com \
--cc=kevinpb@vt.edu \
--cc=linux-rt-users@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.