mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Roman Gushchin <klamm@yandex-team.ru>
To: Kirill Tkhai <tkhai@yandex.ru>, Peter Zijlstra <peterz@infradead.org>
Cc: LKML <linux-kernel@vger.kernel.org>,
	"mingo@redhat.com" <mingo@redhat.com>,
	Artyom Tarasenko <atar4qemu@gmail.com>
Subject: Re: Real-time scheduling policies and hyper-threading
Date: Fri, 25 Apr 2014 15:12:11 +0400	[thread overview]
Message-ID: <9501398424331@webcorp1f.yandex-team.ru> (raw)
In-Reply-To: <968281398370612@web21g.yandex.ru>

25.04.2014, 00:16, "Kirill Tkhai" <tkhai@yandex.ru>:
> 24.04.2014, 22:59, "Peter Zijlstra" <peterz@infradead.org>:
>
> [snip]
>
>>>   Does anyone use rt-scheduler for runtime-like cpu-bound tasks?
>>  So in general cpu bound tasks in the RT classes (FIFO/RR/DEADLINE) are
>>  bad and can make the system go funny.
>>
>>  For general system health it is important that various system tasks
>>  (kthreads usually) can run. Many of these kthreads run at !rt prios, and
>>  by having cpu bound tasks in rt prios they don't get to run.
>
> One more word to this. I had such expirience on 2.6.33 kernel with RT patch
> and weak hardware (sparc32).
>
> Networking was actively used and application did not use any IO operations.
>
> User needs to set all RT priorities by himself. It's necessary to set RT
> priorities at least for softirqs and rcus. RT bandwidth must be switched
> off.

I disable RT bandwidth sharing and change rt_period/rt_runtime to 1/100 ms
respectively.

Thanks,
Roman

  parent reply	other threads:[~2014-04-25 11:17 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-04-24 18:16 Roman Gushchin
2014-04-24 18:58 ` Peter Zijlstra
2014-04-24 20:16   ` Kirill Tkhai
2014-04-24 20:24     ` Peter Zijlstra
2014-04-25 11:12     ` Roman Gushchin [this message]
2014-04-25 11:04   ` Roman Gushchin
2014-04-25 13:16     ` Peter Zijlstra
2014-04-25 15:02       ` Roman Gushchin
2014-04-25 15:11         ` Peter Zijlstra
2014-04-25 16:19           ` Roman Gushchin
2014-04-25 15:16         ` Peter Zijlstra

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=9501398424331@webcorp1f.yandex-team.ru \
    --to=klamm@yandex-team.ru \
    --cc=atar4qemu@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@redhat.com \
    --cc=peterz@infradead.org \
    --cc=tkhai@yandex.ru \
    /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

all inboxes | Powered by JetHome®