All of lore.kernel.org
 help / color / mirror / Atom feed
From: Andrew Morton <akpm@osdl.org>
To: Chris Wright <chrisw@osdl.org>
Cc: jh@sgi.com, limin@engr.sgi.com, linux-kernel@vger.kernel.org,
	jlan@engr.sgi.com, erikj@sgi.com, chrisw@osdl.org
Subject: Re: [PATCH] improving JOB kernel/user interface
Date: Wed, 1 Sep 2004 16:01:27 -0700	[thread overview]
Message-ID: <20040901160127.3ee02f0b.akpm@osdl.org> (raw)
In-Reply-To: <20040901130623.F1924@build.pdx.osdl.net>

Chris Wright <chrisw@osdl.org> wrote:
>
> * John Hesterberg (jh@sgi.com) wrote:
> > The current job /proc ioctl interface is really a fake-syscall interface.
> > We only did that so that our product didn't have to lock into a syscall
> > number that would eventually be used by something else.
> > 
> > The easiest thing for us would probably be to turn it back into a system
> > call, if that would be acceptable for inclusion into the kernel.  We're
> > open to other job interfaces, such as a real /proc character interface,
> > or a new virtual filesystem, or a device driver using ioctls.
> 
> But that system call would still be a single mutliplexor for many calls, right?

Either that, or 19 separate syscalls...

> Not ideal.  Have you tried to map to an fs?

That's worth investigation.

  parent reply	other threads:[~2004-09-01 23:08 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-08-31 22:39 [PATCH] improving JOB kernel/user interface Limin Gu
2004-09-01 19:38 ` John Hesterberg
2004-09-01 20:06   ` Chris Wright
2004-09-01 22:26     ` Limin Gu
2004-09-01 22:30       ` Chris Wright
2004-09-01 23:01     ` Andrew Morton [this message]
2004-09-01 23:25       ` Chris Wright
     [not found] <fa.fbhctle.45ecr4@ifi.uio.no>
2011-11-14 17:17 ` dutuuradu

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=20040901160127.3ee02f0b.akpm@osdl.org \
    --to=akpm@osdl.org \
    --cc=chrisw@osdl.org \
    --cc=erikj@sgi.com \
    --cc=jh@sgi.com \
    --cc=jlan@engr.sgi.com \
    --cc=limin@engr.sgi.com \
    --cc=linux-kernel@vger.kernel.org \
    /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.