Messages in this thread | | | Date | Sat, 28 Apr 2001 16:30:30 +0300 | From | Ville Herva <> | Subject | Re: X15 alpha release: as fast as TUX but in user space |
| |
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 - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
| |