All of lore.kernel.org
 help / color / mirror / Atom feed
From: Olsson John <john.olsson-zlDGZTLOEuz3oGB3hsPCZA@public.gmane.org>
To: "Michal Koutný" <mkoutny-IBi9RG/b67k@public.gmane.org>
Cc: "cgroups-u79uwXL29TY76Z2rM5mHXA@public.gmane.org"
	<cgroups-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>
Subject: RE: [EXTERNAL] Re: Split process across multiple schedulers?
Date: Wed, 16 Mar 2022 08:17:04 +0000	[thread overview]
Message-ID: <77e72fcbbff94977a5179446265c18d2@saabgroup.com> (raw)
In-Reply-To: <20220315173329.GB3780-9OudH3eul5jcvrawFnH+a6VXKuFTiq87@public.gmane.org>

> I think you've complete info now how threads are handled with cgroups.

Thank you for your excellent support! :D


> Good luck with the fork :-)

It's basically already done as part of a Master Thesis. Now we'll
experiment with it and see how theory clashes with the real world. :)


/John

-----Original Message-----
From: Michal Koutný <mkoutny-IBi9RG/b67k@public.gmane.org> 
Sent: den 15 mars 2022 18:34
To: Olsson John <john.olsson-zlDGZTLOEuz3oGB3hsPCZA@public.gmane.org>
Cc: cgroups-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Subject: Re: [EXTERNAL] Re: Split process across multiple schedulers?

On Tue, Mar 15, 2022 at 03:49:52PM +0000, Olsson John <john.olsson@saabgroup.com> wrote:
> As you might have already surmised it was a placeholder example to 
> give the general idea. I think it is time to add some more details. :)

Thanks for sharing the additional description.

> Assume that you have an embedded system running some kind of software 
> with real time like properties. You want to develop and debug your 
> software locally on your high-end machine since it is much more 
> convenient. Alas the software runs way too fast due to the difference 
> in performance so you can't detect overruns etc.

There are certainly more knowledgeable people than me to help with debugging such environments.

> One way of implementing this kind of scheduler would be to create a 
> fork of the FIFO scheduler that have this behavior.

I think you've complete info now how threads are handled with cgroups.

Good luck with the fork :-)


Michal

  parent reply	other threads:[~2022-03-16  8:17 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-03-14 15:19 Split process across multiple schedulers? Olsson John
     [not found] ` <b5039be462e8492085b6638df2a761ca-zlDGZTLOEuz3oGB3hsPCZA@public.gmane.org>
2022-03-14 16:43   ` Michal Koutný
     [not found]     ` <20220314164332.GA20424-9OudH3eul5jcvrawFnH+a6VXKuFTiq87@public.gmane.org>
2022-03-15  8:19       ` [EXTERNAL] " Olsson John
     [not found]         ` <bf2ea0888a9e45d3aafe412f0094cf86-zlDGZTLOEuz3oGB3hsPCZA@public.gmane.org>
2022-03-15 10:35           ` Michal Koutný
     [not found]             ` <20220315103553.GA3780-9OudH3eul5jcvrawFnH+a6VXKuFTiq87@public.gmane.org>
2022-03-15 15:49               ` Olsson John
     [not found]                 ` <84e5b8652edd47d29597d499f29753d6-zlDGZTLOEuz3oGB3hsPCZA@public.gmane.org>
2022-03-15 17:33                   ` Michal Koutný
     [not found]                     ` <20220315173329.GB3780-9OudH3eul5jcvrawFnH+a6VXKuFTiq87@public.gmane.org>
2022-03-16  8:17                       ` Olsson John [this message]
2022-03-16 16:38   ` Tejun Heo
     [not found]     ` <YjIShE3mwRyNbO53-NiLfg/pYEd1N0TnZuCh8vA@public.gmane.org>
2022-03-16 16:49       ` [EXTERNAL] " Olsson John
     [not found]         ` <e9cac4aba6384c5c91125a9f7d61a4e8-zlDGZTLOEuz3oGB3hsPCZA@public.gmane.org>
2022-03-16 17:32           ` Tejun Heo
     [not found]             ` <YjIfMLG5W2a/E4vX-NiLfg/pYEd1N0TnZuCh8vA@public.gmane.org>
2022-03-17  9:30               ` Olsson John

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=77e72fcbbff94977a5179446265c18d2@saabgroup.com \
    --to=john.olsson-zldgztloeuz3ogb3hspcza@public.gmane.org \
    --cc=cgroups-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
    --cc=mkoutny-IBi9RG/b67k@public.gmane.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.