From: Richard Weinberger <richard@nod.at>
To: Thomas Meyer <thomas@m3y3r.de>
Cc: user-mode-linux-devel <user-mode-linux-devel@lists.sourceforge.net>
Subject: Re: [uml-devel] [PATCH] um: Switch clocksource to hrtimers
Date: Sun, 31 May 2015 23:49:54 +0200 [thread overview]
Message-ID: <556B8202.6030501@nod.at> (raw)
In-Reply-To: <1433098827.8871.13.camel@m3y3r.de>
Am 31.05.2015 um 21:00 schrieb Thomas Meyer:
>> Ping.
>> Would be nice to have this patch for the 4.2 merge window.
>
> I can provide you the current version of the patch, but I'm not sure if
> it's ready for inclusion yet.
That's fine. I'll look at it.
Just rebase it against Linus' tree or uml-next.
https://git.kernel.org/cgit/linux/kernel/git/rw/uml.git/log/?h=linux-next
> For example:
> - With this patch I see new zombie processes of UML userspace
> processes. I'm not sure what's going on here.
> - Anton reported some hang he sees with this patch
> - A person from cicso is worried about the potential idle CPU usage
> after the patch, because of the many timers started, i.e. a host with
> hundreds of UMLs.
>
> Also meanwhile I think is not the correct thing to start a new timer
> for each UML userspace process, because the timer will also trigger the
> userspace process, even the corresponding process isn't scheduled by
> the kernel currently. I think the previous behaviour with the itimer
> was okay, because the virtual timer only did execute when the process
> was executing which is the correct thing to do for the currently active
> task in the UML kernel.
> I see two solutions for above problem: cascade the kernel timer into
> the current active task; there is actually no need to start a timer in
> each userspace process.
> Start/stop each timer when a userspace process becomes active resp.
> becomes inactive again.
> I hope above logic makes some sense at all! What do you think about
> this?
Hm, we definitely don't want a new timer for each userspace proc. The timer
has to work as a regular clock source.
But I'll have to read your/Anton's code in detail first.
Thanks,
//richard
------------------------------------------------------------------------------
_______________________________________________
User-mode-linux-devel mailing list
User-mode-linux-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/user-mode-linux-devel
next prev parent reply other threads:[~2015-05-31 21:50 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-05-17 9:25 [uml-devel] [PATCH] um: Switch clocksource to hrtimers Thomas Meyer
2015-05-19 16:19 ` Anton Ivanov
2015-05-19 16:39 ` Richard Weinberger
2015-05-19 16:47 ` Anton Ivanov
2015-05-19 22:12 ` Richard Weinberger
2015-05-20 5:26 ` Thomas Meyer
2015-05-31 11:15 ` Richard Weinberger
2015-05-31 19:00 ` Thomas Meyer
2015-05-31 19:10 ` Anton Ivanov
2015-06-04 10:04 ` Thomas Meyer
2015-06-04 10:37 ` Anton Ivanov
2015-06-25 18:00 ` Thomas Meyer
2015-05-31 21:49 ` Richard Weinberger [this message]
2015-05-31 21:58 ` Thomas Meyer
-- strict thread matches above, loose matches on Subject: below --
2015-08-09 17:53 Thomas Meyer
2015-08-15 8:15 ` Richard Weinberger
2015-08-15 16:27 ` Anton Ivanov
2015-08-18 9:34 ` Richard Weinberger
2015-08-18 15:30 ` Anton Ivanov
2015-08-18 16:04 ` Thomas Meyer
2015-10-13 21:45 ` Richard Weinberger
2015-10-14 6:12 ` Anton Ivanov
2015-10-14 8:25 ` Thomas Meyer
2015-10-14 9:23 ` Anton Ivanov
2015-10-14 11:22 ` Thomas Meyer
2015-10-16 9:18 ` Anton Ivanov
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=556B8202.6030501@nod.at \
--to=richard@nod.at \
--cc=thomas@m3y3r.de \
--cc=user-mode-linux-devel@lists.sourceforge.net \
/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