From: Anton Ivanov <anton.ivanov@kot-begemot.co.uk>
To: Richard Weinberger <richard.weinberger@gmail.com>
Cc: "user-mode-linux-devel@lists.sourceforge.net"
<user-mode-linux-devel@lists.sourceforge.net>
Subject: Re: [uml-devel] [UM] Long loop in __getnsdayoftime() after resume from ram
Date: Mon, 27 Apr 2015 09:20:12 +0100 [thread overview]
Message-ID: <553DF13C.6080806@kot-begemot.co.uk> (raw)
In-Reply-To: <CAFLxGvwD0s37G0GGi3BzBgAAbWRK6AjEPBUXE2yzQChBXQyjFA@mail.gmail.com>
On 27/04/15 08:23, Richard Weinberger wrote:
> On Mon, Apr 27, 2015 at 7:47 AM, Anton Ivanov
> <anton.ivanov@kot-begemot.co.uk> wrote:
>> On 26/04/15 22:00, Richard Weinberger wrote:
>>>>> Can you give the attached patch a try?
>>>>> Let's see if it proves my theory.
>>>>> Looks like UML's clocksource needs fixing.
>>>> Hi Richard,
>>>>
>>>> I did run this for an hour and did 4 suspend/resume cycles and it seems
>>>> not to hang any more!
>>> Yay!
>>> BTW: Changing the host's time should also work for testing...
>>>
>>>> I'll test your other patch the next week, but AFAIU using clock_gettime
>>>> should solve this hangs in a sane way.
>>> Yep. I have no idea why UML is currently using gettimeofday() as clocksource,
>>> this is completely bogus. ;-\
>> It is even more bogus than you think - read time.c, it is using itimer
>> on the virtual clock for all timers for extra spice so the timers are
>> dependent on how much cpu it uses at any given time.
> Yep.
>
>> It does not need to be - I wrote a patchset for it to use posix timers
>> and CLOCK_MONOTONIC. It went into Richard's queue ~ a year ago along
>> with an epoll based IRQ controller and some vNIC drivers.
>>
>> Have not heard of it since.
> mea culpa!
> If I forget a patch, just shout at me.
>
> Can you please rebase your patches against 4.1-rc1?
Sure.
I will do my best to sort it out by ~ Tue next week latest. I am working
mostly on opendaylight now so I will have to do it in my free time.
> Such that I can merge them ASAP...
>
There were several patches in that patchset, I suggest we try to do it
step-by-step - merge only the timer and the epoll controller on first
pass (while they are not dependent, they have not seen extensive testing
separately). This is what I will re-submit as a "first pass".
These are prerequisites for the network interfaces, etc which we can do
later. The last tests I did in my previous job on them were showing >
3GBit/s forwarding rate across a UML instance pinned to a single core
and measured to a remote network device (real forwarding rate on real
network traffic - not moving packets locally on the host).
A.
------------------------------------------------------------------------------
One dashboard for servers and applications across Physical-Virtual-Cloud
Widest out-of-the-box monitoring support with 50+ applications
Performance metrics, stats and reports that give you Actionable Insights
Deep dive visibility with transaction tracing using APM Insight.
http://ad.doubleclick.net/ddm/clk/290420510;117567292;y
_______________________________________________
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-04-27 8:20 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-10-20 9:51 [uml-devel] [UM] Long loop in __getnsdayoftime() after resume from ram Thomas Meyer
2014-10-20 9:56 ` Richard Weinberger
2014-10-20 19:19 ` Thomas Meyer
2015-04-24 19:58 ` Thomas Meyer
2015-04-26 18:32 ` Richard Weinberger
2015-04-26 20:20 ` Richard Weinberger
2015-04-26 20:57 ` Thomas Meyer
2015-04-26 21:00 ` Richard Weinberger
2015-04-27 5:47 ` Anton Ivanov
2015-04-27 7:23 ` Richard Weinberger
2015-04-27 8:20 ` Anton Ivanov [this message]
2015-04-30 16:40 ` Thomas Meyer
-- strict thread matches above, loose matches on Subject: below --
2014-10-19 12:39 Thomas Meyer
2014-10-20 8:27 ` Richard Weinberger
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=553DF13C.6080806@kot-begemot.co.uk \
--to=anton.ivanov@kot-begemot.co.uk \
--cc=richard.weinberger@gmail.com \
--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