Date: Thu, 02 Dec 1999 12:34:29 -0500 From: "Daniel M. Eischen" <eischen@vigrid.com> To: "Daniel C. Sobral" <dcs@newsguy.com> Cc: Jake Burkholder <jburkhol@home.com>, Julian Elischer <julian@whistle.com>, arch@freebsd.org Subject: Re: Threads stuff Message-ID: <3846ADA5.72017F25@vigrid.com> References: <19991127223909.22A511FCF@io.yi.org> <3846A720.2BA461A6@newsguy.com>
next in thread | previous in thread | raw e-mail | index | archive | help
"Daniel C. Sobral" wrote: > > Jake Burkholder wrote: > > > > I'm just going from what Daniel said about libc_r having > > to get the time of day and set the interval timer in > > order to do a context switch, which can probably be > > done in one system call. Either the context can be > > Mmmm... I though gettimeofday() was a very slow system call... I'll > have to check that. Where's the rest of this thread? Not to say that clock_gettime is any better, but gettimeofday was used probably because clock_gettime didn't/doesn't exist in FreeBSD-2.x. If anyone is going to be measuring context switch times of the current libc_r, please remember that there are at least a couple of extra system calls per thread switch (gettimeofday and setitimer). And if there are any threads doing I/O, there will be an additional poll(). Dan Eischen eischen@vigrid.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-arch" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?3846ADA5.72017F25>