From: "Guillaume Chazarain" <guichaz@gmail.com>
To: "Ingo Molnar" <mingo@elte.hu>
Cc: "Linus Torvalds" <torvalds@linux-foundation.org>,
linux-kernel@vger.kernel.org,
"Andrew Morton" <akpm@linux-foundation.org>
Subject: Re: [git pull] scheduler changes for v2.6.26
Date: Sat, 19 Apr 2008 20:47:21 +0200 [thread overview]
Message-ID: <3d8471ca0804191147q3af7f01ei86b23b75bd0eb559@mail.gmail.com> (raw)
In-Reply-To: <20080419181304.GB21353@elte.hu>
On 4/19/08, Ingo Molnar <mingo@elte.hu> wrote:
> Guillaume Chazarain (1):
> sched: fix rq->clock overflows detection with CONFIG_NO_HZ
This one should have been dropped (per http://lkml.org/lkml/2008/1/25/413)
I don't like rq->clock relying on jiffies, and you already fixed the
original manifestation of the problem in:
commit 2997c8c4a0b179e8b834a7f30ba4323f2c60ccf4
Author: Ingo Molnar <mingo@elte.hu>
Date: Fri Jan 11 13:35:54 2008 +0100
block: fix blktrace timestamps
David Dillow reported broken blktrace timestamps. The reason
is cpu_clock() which is not a global time source.
Fix bkltrace timestamps by using ktime_get() like the networking
code does for packet timestamps. This also removes a whole lot
of complexity from bkltrace.c and shrinks the code by 500 bytes:
text data bss dec hex filename
2888 124 44 3056 bf0 blktrace.o.before
2390 116 44 2550 9f6 blktrace.o.after
Signed-off-by: Ingo Molnar <mingo@elte.hu>
Signed-off-by: Jens Axboe <jens.axboe@oracle.com>
--
Guillaume
next prev parent reply other threads:[~2008-04-19 18:47 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-04-19 18:13 Ingo Molnar
2008-04-19 18:47 ` Guillaume Chazarain [this message]
2008-04-19 18:49 ` Ingo Molnar
2008-04-19 18:54 ` Peter Zijlstra
2008-04-19 19:47 ` Frans Pop
2008-04-21 12:39 ` Ingo Molnar
2008-04-21 16:31 ` Frans Pop
2008-04-21 19:43 ` Ingo Molnar
2008-04-22 8:51 ` Mike Galbraith
2008-04-22 8:59 ` Ingo Molnar
2008-04-22 9:59 ` Peter Zijlstra
2008-04-22 12:25 ` Mike Galbraith
2008-04-23 8:11 ` Mike Galbraith
2008-04-23 10:30 ` Mike Galbraith
2008-04-23 11:21 ` Peter Zijlstra
2008-04-23 13:27 ` Mike Galbraith
2008-04-22 9:41 ` Kevin Winchester
2008-04-22 10:49 ` David Miller
2008-04-22 11:10 ` Peter Zijlstra
2008-04-23 9:36 ` Frans Pop
2008-04-23 9:42 ` Peter Zijlstra
2008-04-23 9:46 ` Ingo Molnar
2008-04-23 13:36 ` Frans Pop
2008-04-29 12:29 ` Ingo Molnar
2008-04-29 15:28 ` Steven Rostedt
2008-04-23 16:23 ` Frans Pop
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=3d8471ca0804191147q3af7f01ei86b23b75bd0eb559@mail.gmail.com \
--to=guichaz@gmail.com \
--cc=akpm@linux-foundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=torvalds@linux-foundation.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®