From: Samuel Tardieu <sam@rfc1149.net>
To: linux-kernel@vger.kernel.org
Subject: Re: How is Code in do_sys_settimeofday() safe in case of SMP and Nest Kernel Path?
Date: 02 Oct 2006 12:12:34 +0200 [thread overview]
Message-ID: <87hcynm3fx.fsf@willow.rfc1149.net> (raw)
In-Reply-To: Pine.LNX.4.64.0609301015060.3519@schroedinger.engr.sgi.com
>>>>> "Christoph" == Christoph Lameter <clameter@sgi.com> writes:
Christoph> I really hate adding overhead to gettimeofday() and we
Christoph> would have to take the seqlock in all places when we
Christoph> reference tz. Maybe we can tolerate the resulting race?
Agreed. In some applications, gettimeofday() is called an awfully lot
of times. And the only plausible case where settimeofday() is called
after boot is on a multi-core laptop during a traval accross different
timezones, where it is unlikely that time-and-DST-sensitive
applications would be running.
Sam
--
Samuel Tardieu -- sam@rfc1149.net -- http://www.rfc1149.net/
prev parent reply other threads:[~2006-10-02 10:20 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-09-29 14:33 How is Code in do_sys_settimeofday() safe in case of SMP and Nest Kernel Path? Dong Feng
2006-09-29 16:05 ` Christoph Lameter
2006-09-29 16:16 ` Dong Feng
2006-09-30 14:37 ` Nick Piggin
2006-09-30 15:03 ` Andi Kleen
2006-09-30 17:13 ` Christoph Lameter
2006-10-02 10:08 ` Samuel Tardieu
2006-10-03 8:03 ` Pavel Machek
2006-10-03 10:03 ` Andi Kleen
2006-09-30 16:09 ` Dong Feng
2006-09-30 17:26 ` Christoph Lameter
2006-10-01 3:48 ` Nick Piggin
2006-10-01 12:22 ` Dong Feng
2006-10-02 10:12 ` Samuel Tardieu [this message]
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=87hcynm3fx.fsf@willow.rfc1149.net \
--to=sam@rfc1149.net \
--cc=linux-kernel@vger.kernel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox