mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Ville Herva <vherva@mail.niksula.cs.hut.fi>
To: Ingo Molnar <mingo@elte.hu>
Cc: Fabio Riccardi <fabio@chromium.com>, linux-kernel@vger.kernel.org
Subject: Re: X15 alpha release: as fast as TUX but in user space
Date: Sat, 28 Apr 2001 16:30:30 +0300	[thread overview]
Message-ID: <20010428163030.D3682@niksula.cs.hut.fi> (raw)
In-Reply-To: <20010428161502.I3529@niksula.cs.hut.fi> <Pine.LNX.4.33.0104281521210.10295-100000@localhost.localdomain>
In-Reply-To: <Pine.LNX.4.33.0104281521210.10295-100000@localhost.localdomain>; from mingo@elte.hu on Sat, Apr 28, 2001 at 03:24:25PM +0200

On Sat, Apr 28, 2001 at 03:24:25PM +0200, you [Ingo Molnar] claimed:
> 
> On Sat, 28 Apr 2001, Ville Herva wrote:
> 
> > Uhh, perhaps I'm stupid, but why not cache the date field and update
> > the field once a five seconds? Or even once a second?
> 
> perhaps the best way would be to do this updating in the sending code
> itself.
> 
> first there would be a 'current time thread', which updates a global
> shared variable that shows the current time. (ie. no extra system-call is
> needed to access current time.) If the header-sending code detects that
> current time is not equal to the timestamp stored in the header itself,
> then the header is reconstructed. Pretty simple.

Yes, that's vaguely resembles what I had in mind. Of course I had no idea
about the data structures Tux or X15 use internally, so I couldn't think it
too thoroughly.


-- v --

v@iki.fi

  reply	other threads:[~2001-04-28 13:30 UTC|newest]

Thread overview: 32+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-04-28  0:18 Fabio Riccardi
2001-04-28  0:41 ` Aaron Lehmann
2001-04-28  0:49 ` David S. Miller
2001-04-28  1:11   ` Fabio Riccardi
2001-04-28  8:42 ` Ingo Molnar
2001-04-28 13:15   ` Ville Herva
2001-04-28 13:21     ` Ingo Molnar
2001-04-28 13:24     ` Ingo Molnar
2001-04-28 13:30       ` Ville Herva [this message]
2001-04-28 13:55         ` Andi Kleen
2001-04-29 21:25   ` Fabio Riccardi
2001-04-30  5:43     ` dean gaudet
2001-04-30 19:36       ` Fabio Riccardi
2001-04-30 21:47         ` dean gaudet
2001-04-30 21:52         ` David S. Miller
2001-05-01  7:31         ` Ingo Molnar
2001-04-30  6:39     ` David S. Miller
2001-05-01  7:25     ` Ingo Molnar
2001-04-28  7:32 Ingo Molnar
2001-04-29 21:19 ` Fabio Riccardi
2001-05-01  8:53   ` Ingo Molnar
2001-05-01 17:10     ` Fabio Riccardi
2001-05-01 17:12       ` Ingo Molnar
2001-05-04  1:58         ` Fabio Riccardi
2001-05-04  8:49           ` Ingo Molnar
2001-05-04 18:10             ` Fabio Riccardi
2001-05-04 18:38               ` Davide Libenzi
2001-05-09 22:42             ` Fabio Riccardi
2001-05-02  8:50   ` Ingo Molnar
2001-05-02 14:12     ` Zach Brown
2001-05-03  2:41       ` Fabio Riccardi
2001-05-02 23:19   ` Lincoln Dale

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=20010428163030.D3682@niksula.cs.hut.fi \
    --to=vherva@mail.niksula.cs.hut.fi \
    --cc=fabio@chromium.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@elte.hu \
    /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®