From: john stultz <johnstul@us.ibm.com>
To: Serge Belyshev <belyshev@depni.sinp.msu.ru>
Cc: Ingo Molnar <mingo@elte.hu>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: [RT] fix delay in do_vgettimeofday() in arch/x86_64/kernel/vsyscall.c
Date: Fri, 09 Dec 2005 18:33:40 -0800 [thread overview]
Message-ID: <1134182041.4002.10.camel@leatherman> (raw)
In-Reply-To: <87d5k6ukky.fsf@foo.vault.bofh.ru>
On Fri, 2005-12-09 at 22:38 +0300, Serge Belyshev wrote:
>
> There are occasional very very long (30..60 sec) delays happening when calling
> gettimeofday() vsyscall on x86_64 with 2.6.14-rt22 kernel.
>
> These delays come from while() looping over invalid data that are
> going to be discarded by seqlock.
Ah, good catch! I just included a similar change (moved all the math
outside the lock) in my own tree.
Thanks for finding this!
-john
next prev parent reply other threads:[~2005-12-10 2:34 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-12-09 19:38 [RT] fix delay in do_vgettimeofday() in arch/x86_64/kernel/vsyscall.c Serge Belyshev
2005-12-10 2:33 ` john stultz [this message]
2005-12-10 20:56 ` Fernando Lopez-Lezcano
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=1134182041.4002.10.camel@leatherman \
--to=johnstul@us.ibm.com \
--cc=belyshev@depni.sinp.msu.ru \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
/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