public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: anton wilson <anton.wilson@camotion.com>
To: linux-kernel@vger.kernel.org
Subject: do_gettimeofday vs. rdtsc in the scheduler
Date: Mon, 9 Sep 2002 18:21:57 -0400	[thread overview]
Message-ID: <200209092232.SAA05145@nealtech.net> (raw)



I'm writing a patch for the scheduler that allows normal processes to run 
occasionally even though real-time processes completely dominate the CPU. In 
order to do this the way I want to for a specific real-time application, I 
need to keep track of the times that the schedule(void) function gets called. 
This time is then used to calculate the time difference between when a normal 
process was run last and the current time. I was trying to avoid 
do_gettimeofday because of the overhead, but now I'm wondering if rdtsc on an 
SMP machine may mess up my readings because the TSC from two different 
processors may be read. Am I right in assuming this? Secondly, any good 
suggestions on how to proceed with my patch? 


Thanks,

Anton

             reply	other threads:[~2002-09-09 22:29 UTC|newest]

Thread overview: 29+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-09-09 22:21 anton wilson [this message]
     [not found] <200209172020.g8HKKPF13227@eng2.beaverton.ibm.com>
2002-09-17 20:29 ` Fwd: do_gettimeofday vs. rdtsc in the scheduler john stultz
2002-09-17 20:39   ` David S. Miller
2002-09-17 20:57     ` john stultz
2002-09-17 20:56       ` David S. Miller
     [not found] <200209172020.g8HKKPF13227@eng2.beaverton.ibm.com.suse.lists.linux.kernel>
     [not found] ` <1032294559.22815.180.camel@cog.suse.lists.linux.kernel>
     [not found]   ` <20020917.133933.69057655.davem@redhat.com.suse.lists.linux.kernel>
2002-09-17 21:00     ` Andi Kleen
2002-09-17 20:54       ` David S. Miller
2002-09-17 21:28         ` Alan Cox
2002-09-17 21:18           ` David S. Miller
2002-09-17 22:02             ` James Cleverdon
2002-09-17 22:44               ` Andi Kleen
2002-09-17 22:38                 ` David S. Miller
2002-09-17 22:55                   ` James Cleverdon
2002-09-17 23:12                     ` David S. Miller
2002-09-17 23:32                       ` john stultz
2002-09-17 23:32                         ` David S. Miller
2002-09-17 23:52                           ` Andi Kleen
2002-09-17 23:46                             ` David S. Miller
2002-09-17 23:58                               ` Andi Kleen
2002-09-17 23:51                                 ` David S. Miller
2002-09-18  0:05                                   ` Andi Kleen
2002-09-18  1:04                                     ` James Cleverdon
2002-09-19 18:02                                       ` Andrea Arcangeli
2002-09-20 11:04                                     ` Maciej W. Rozycki
2002-09-19 11:20                                 ` Mikael Pettersson
2002-09-19 13:27                                   ` Alan Cox
2002-09-19 13:39                                     ` Mikael Pettersson
2002-09-20 15:26                                     ` John Levon
2002-09-18  6:40               ` Vojtech Pavlik
2002-09-19 18:04                 ` Andrea Arcangeli

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=200209092232.SAA05145@nealtech.net \
    --to=anton.wilson@camotion.com \
    --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