From: Andrew Morton <akpm@linux-foundation.org>
To: "Jakub W. Jozwicki" <jozwicki@aster.pl>
Cc: linux-kernel@vger.kernel.org
Subject: Re: sched_yield() on 2.6.25
Date: Mon, 9 Jun 2008 02:35:18 -0700 [thread overview]
Message-ID: <20080609023518.4a7d9868.akpm@linux-foundation.org> (raw)
In-Reply-To: <200806081334.10875.jozwicki@aster.pl>
On Sun, 8 Jun 2008 13:34:10 +0200 "Jakub W. Jozwicki" <jozwicki@aster.pl> wrote:
> Hello,
> I observe strange behavior of sched_yield() on 2.6.25 (strange comparing to
> 2.6.24). Here is the code (available at
> http://systest.googlecode.com/files/systest20080119.tgz):
>
> ------------------------------------------------------
> timer_t timer;
> sig_atomic_t cnt = 0;
> long long sum = 0;
> long times[21], min, max;
> pthread_mutex_t mutex = PTHREAD_MUTEX_INITIALIZER;
> struct timespec ts = { 0, 0 };
> pthread_t last_th = 0;
>
> void *th_proc(void* p) {
> int n = SIZE(times) -1;
> pthread_t th;
>
> while(1) {
> pthread_mutex_lock(&mutex);
> th = pthread_self();
> if (pthread_equal(th,last_th)) {
> pthread_mutex_unlock(&mutex);
> sched_yield();
> continue;
> }
> rt_timer_stop(&ts);
> last_th = th;
> if (cnt>=1) {
> times[cnt-1] = ts_sum(&ts);
> if (cnt <= n) {
> sum += times[cnt-1];
> box(times[cnt-1],min,max);
> #define uint unsigned int
> printf("[%u] Thread switching time: %ldns\n",(uint)th, times[cnt-1]);
> }
> else {
> printf("[%u] Thread switching time (not counted): %ldns\n",(uint)th,
> times[cnt-1]);
> }
> cnt--;
> }
> ....
> -----------------------------------------------------
> and here are the results:
>
> Setting cpu mask to 1
>
> -- SYSTEM INFO -------------------
>
> localhost: Linux 2.6.24-rt4 #8 SMP PREEMPT RT Mon Jan 21 18:45:00 CET 2008
>
> Setting priority SCHED_OTHER to 0 (normal process) for 20802
> [3084102544] Thread switching time (not counted): 10709015ns
> [3075709840] Thread switching time: 35468301ns
> [3084102544] Thread switching time: 2793ns
> [3075709840] Thread switching time 30725ns
> [3084102544] Thread switching time: 10405ns
> [3075709840] Thread switching time: 2724ns
> [3084102544] Thread switching time: 2654ns
> [3075709840] Thread switching time: 2653ns
> [3084102544] Thread switching time: 3352ns
> [3075709840] Thread switching time: 2583ns
> [3084102544] Thread switching time: 2514ns
> [3075709840] Thread switching time: 2514ns
It would save us some time if you were to tell us what these results
mean, please.
next prev parent reply other threads:[~2008-06-09 9:35 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-06-08 11:34 sched_yield() on 2.6.25 Jakub W. Jozwicki
2008-06-09 9:35 ` Andrew Morton [this message]
[not found] <fa.5iKTy3xTJkKWZLGio+GIHXi3+0o@ifi.uio.no>
2008-06-08 22:09 ` Robert Hancock
2008-06-09 6:37 ` Jakub Jozwicki
2008-06-09 9:03 ` Helge Hafting
2008-06-09 15:04 ` Peter Zijlstra
[not found] <aCBfw-3Cv-23@gated-at.bofh.it>
[not found] ` <aCBfw-3Cv-21@gated-at.bofh.it>
[not found] ` <aCJd6-3IF-11@gated-at.bofh.it>
[not found] ` <aCRaM-8cM-33@gated-at.bofh.it>
2008-06-11 15:28 ` Bodo Eggert
2008-06-11 22:45 ` Leon Woestenberg
2008-06-12 8:09 ` Helge Hafting
2008-06-12 22:33 ` Bodo Eggert
2008-06-13 8:37 ` Helge Hafting
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=20080609023518.4a7d9868.akpm@linux-foundation.org \
--to=akpm@linux-foundation.org \
--cc=jozwicki@aster.pl \
--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