From: Arjan van de Ven <arjanv@redhat.com>
To: Martin Schwidefsky <schwidefsky@de.ibm.com>
Cc: akpm@osdl.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] s390 (9/9): no timer interrupts in idle.
Date: Thu, 22 Apr 2004 15:11:36 +0200 [thread overview]
Message-ID: <20040422131135.GA7589@devserv.devel.redhat.com> (raw)
In-Reply-To: <OF8486E763.A98E66AA-ONC1256E7E.00452A1A-C1256E7E.0045F93D@de.ibm.com>
[-- Attachment #1: Type: text/plain, Size: 846 bytes --]
On Thu, Apr 22, 2004 at 02:44:17PM +0200, Martin Schwidefsky wrote:
>
>
>
>
> > xtime is easy, that's interpolated anyway afaics. Jiffies would either
> just
> > jump some, which code needs to deal with anyway given that preempt can do
> > the same, or would become an approximated thing as well based on the
> other
> > time keeping sources in the system.
>
> Unluckily no. xtime is not easy because the network stack uses this for
> time stamps at several locations. Living in the past and time stamps for
> network packets don't go together, do they?
I thought this got fixed last week. But as I said it's easy to interpolate.
> By the way I am planning to do a BOFS at the OLS in july where I'd like
> to discuss exactly this kind of questions. Any chance that you'd be there
> too?
quite possible, I haven't booked my flight yet tho
[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]
next prev parent reply other threads:[~2004-04-22 13:12 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-04-22 12:44 [PATCH] s390 (9/9): no timer interrupts in idle Martin Schwidefsky
2004-04-22 13:11 ` Arjan van de Ven [this message]
2004-04-23 3:32 ` George Anzinger
-- strict thread matches above, loose matches on Subject: below --
2004-04-29 8:24 Martin Schwidefsky
2004-04-29 12:06 ` Dipankar Sarma
2004-04-29 7:43 Martin Schwidefsky
2004-04-29 8:16 ` Dipankar Sarma
2004-04-23 8:48 Martin Schwidefsky
2004-04-22 14:56 Martin Schwidefsky
2004-04-28 19:07 ` Dipankar Sarma
2004-04-22 12:14 Martin Schwidefsky
2004-04-22 12:25 ` Arjan van de Ven
2004-04-22 11:09 Martin Schwidefsky
2004-04-22 11:14 ` Arjan van de Ven
2004-04-22 10:53 Martin Schwidefsky
2004-04-22 10:56 ` Arjan van de Ven
2004-04-22 8:55 Martin Schwidefsky
2004-04-22 8:48 Martin Schwidefsky
2004-04-22 8:52 ` Arjan van de Ven
[not found] <1Nt5d-84u-3@gated-at.bofh.it>
[not found] ` <1NwPD-2RW-37@gated-at.bofh.it>
[not found] ` <1NwPE-2RW-39@gated-at.bofh.it>
[not found] ` <1Nx8Y-3ev-15@gated-at.bofh.it>
2004-04-21 22:38 ` Andi Kleen
2004-04-21 18:52 Martin Schwidefsky
2004-04-21 21:58 ` Dipankar Sarma
2004-04-21 16:37 Martin Schwidefsky
2004-04-21 20:43 ` Dipankar Sarma
2004-04-21 20:46 ` Christoph Hellwig
2004-04-21 21:01 ` Dipankar Sarma
2004-04-21 16:31 Martin Schwidefsky
2004-04-21 16:32 ` Christoph Hellwig
2004-04-21 14:49 Martin Schwidefsky
2004-04-21 15:31 ` Christoph Hellwig
2004-04-22 8:02 ` Arjan van de Ven
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=20040422131135.GA7589@devserv.devel.redhat.com \
--to=arjanv@redhat.com \
--cc=akpm@osdl.org \
--cc=linux-kernel@vger.kernel.org \
--cc=schwidefsky@de.ibm.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.