Skip site navigation (1)Skip section navigation (2)
Date:      Tue, 21 Jan 2003 10:06:40 -0800
From:      Peter Wemm <peter@wemm.org>
To:        phk@freebsd.org
Cc:        Robert Watson <rwatson@freebsd.org>, Matthew Dillon <dillon@apollo.backplane.com>, Terry Lambert <tlambert2@mindspring.com>, "Alan L. Cox" <alc@imimic.com>, arch@freebsd.org
Subject:   Re: getsysfd() patch #1 (Re: Virtual memory question) 
Message-ID:  <20030121180640.956922A7EA@canning.wemm.org>
In-Reply-To: <3077.1042730640@critter.freebsd.dk> 

next in thread | previous in thread | raw e-mail | index | archive | help
phk@freebsd.org wrote:
> In message <Pine.NEB.3.96L.1030116100226.59693C-100000@fledge.watson.org>, Ro
    be
> rt Watson writes:
> >
> >On Wed, 15 Jan 2003, Matthew Dillon wrote:
> >
> >>     I think we've established the usefulness of a VM Object descriptor.  N
    ow
> >>     what about the system call API?  At the moment I have:
> >
> >Since we appear to be building a new API and IPC semantic from the ground
> >up, I think it would be worthwhile to look at some of the other weird,
> >wonderful, or perhaps just bizarre, things that others have done in the
> >past.
> 
> I would like to see it being developed, tested, benchmarked and find
> at least one application before we add YAIPC to FreeBSD's sources...

Also, I think the proposed API where this stuff is overloaded into a single
syscall is a bad idea, *especially* when we have millions of syscalls
available.  Personally, I'd prefer a simpler:
  #include <unistd.h>
  int fd = memfd(off_t size);
type API, and if a compelling need for the timer stuff (or whatever)
turns up, then create the correct syscalls for those.  I dont much care
if they use a single common DTYPE_SYSFD file type or something, but please
lets not paint ourselves into a corner like what happened with semsys(),
msgsys(), etc.  We're still paying for that syscall overloading mistake
and still have not recovered from it.  5.0-RELEASE still tries to use
them..  check out all the nasty code in libc for it (and on the other
platforms).

I'm not saying the timer stuff isn't needed, just that it should be exposed
to userland seperately with the correct (to be determined for timers) API.

Cheers,
-Peter
--
Peter Wemm - peter@wemm.org; peter@FreeBSD.org; peter@yahoo-inc.com
"All of this is for nothing if we don't go to the stars" - JMS/B5


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?20030121180640.956922A7EA>