mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Roland McGrath <roland@redhat.com>
To: Nick Piggin <nickpiggin@yahoo.com.au>
Cc: Linus Torvalds <torvalds@osdl.org>, Andrew Morton <akpm@osdl.org>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	Ulrich Drepper <drepper@redhat.com>,
	Christoph Lameter <clameter@sgi.com>
Subject: Re: [PATCH] CPU time clock support in clock_* syscalls
Date: Tue, 5 Oct 2004 17:33:35 -0700	[thread overview]
Message-ID: <200410060033.i960XZ0S007852@magilla.sf.frob.com> (raw)
In-Reply-To: Nick Piggin's message of  Wednesday, 6 October 2004 09:18:10 +1000 <41632BB2.6000202@yahoo.com.au>

> It seemed like a syscall could read the values from a task currently
> running on another CPU. If not, great.

Indeed it can.  And yes, there is no locking against updates for this.  For
sched_time on 32-bit platforms, there is the possibility it could be read
during an update and give a bogus value if the high half is updated before
the low half.  Since there are no guarantees about accuracy, period, I
decided not to worry about such an anomaly.  Perhaps it would be better to
do something about this, but AFAIK nothing perfect can be done without
adding more words to task_struct (e.g. seqcount).  I don't know if the
nature of SMP cache behavior makes something like:

	do {
		sample = p->sched_time;
	} while (p->sched_time != sample);

sufficient.  That would certainly be easy to do.


Thanks,
Roland

  reply	other threads:[~2004-10-06  0:34 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-10-05  5:15 Roland McGrath
2004-10-05  5:20 ` Andrew Morton
2004-10-05  5:27   ` Roland McGrath
2004-10-05  6:43 ` Nick Piggin
2004-10-05 18:28   ` Roland McGrath
2004-10-05 23:18     ` Nick Piggin
2004-10-06  0:33       ` Roland McGrath [this message]
2004-10-06  0:51         ` Nick Piggin
2004-10-05 15:39 ` Christoph Lameter
2004-10-05 18:38   ` Roland McGrath
2004-10-05 20:53     ` Christoph Lameter
2004-10-05 21:22       ` Roland McGrath
2004-10-05 21:28         ` Christoph Lameter
2004-10-06  0:35           ` Roland McGrath
2004-10-06  1:21             ` Christoph Lameter
2004-10-07 19:45               ` Roland McGrath
2004-10-07 20:24                 ` Christoph Lameter
2004-10-05 17:29 ` Christoph Lameter

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=200410060033.i960XZ0S007852@magilla.sf.frob.com \
    --to=roland@redhat.com \
    --cc=akpm@osdl.org \
    --cc=clameter@sgi.com \
    --cc=drepper@redhat.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=nickpiggin@yahoo.com.au \
    --cc=torvalds@osdl.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

all inboxes | Powered by JetHome®