From: Arjan van de Ven <arjanv@redhat.com>
To: chas williams <chas@locutus.cmf.nrl.navy.mil>
Cc: Christoph Hellwig <hch@infradead.org>,
David Howells <dhowells@redhat.com>,
torvalds@transmeta.com, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] add a stub by which a module can bind to the AFS syscall
Date: 30 Apr 2003 17:50:45 +0200 [thread overview]
Message-ID: <1051717845.1403.16.camel@laptop.fenrus.com> (raw)
In-Reply-To: <200304301533.h3UFXvGi023489@locutus.cmf.nrl.navy.mil>
[-- Attachment #1: Type: text/plain, Size: 682 bytes --]
On Wed, 2003-04-30 at 17:33, chas williams wrote:
> In message <20030430162739.A9255@infradead.org>,Christoph Hellwig writes:
> >So fix the AFS code up to use a routine for each subcall that
> >can still map to pioctl for !linux. After that we can continue the
> >discussion on how these calls are best implemented on linux.
>
> because time is precious its quite a bit easier to fix one spot in
> the linux kernel than to fix a hundred or so in the afs code.
ehm no.
There is no valid AFS code using this since there is no syscall yet ;)
And it IS more work for linux, since 32 bit emulation on 64 bit machines
will be a MAJOR pain if everything is this opaque.
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 189 bytes --]
next prev parent reply other threads:[~2003-04-30 15:38 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-04-30 13:44 [PATCH] add a stub by which a module can bind to the AFS syscall David Howells
2003-04-30 14:02 ` Christoph Hellwig
2003-04-30 14:46 ` Jeff Garzik
2003-04-30 14:55 ` Christoph Hellwig
2003-04-30 14:57 ` chas williams
2003-04-30 15:02 ` Christoph Hellwig
2003-04-30 15:13 ` chas williams
2003-04-30 15:27 ` Christoph Hellwig
2003-04-30 15:33 ` chas williams
2003-04-30 15:38 ` Christoph Hellwig
2003-04-30 15:50 ` Arjan van de Ven [this message]
2003-04-30 15:42 ` Anton Blanchard
2003-04-30 15:56 ` viro
2003-05-08 14:01 ` David Howells
2003-04-30 15:30 ` David Howells
2003-04-30 15:37 ` Christoph Hellwig
2003-04-30 18:07 ` Jan Harkes
2003-04-30 18:19 ` Trond Myklebust
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=1051717845.1403.16.camel@laptop.fenrus.com \
--to=arjanv@redhat.com \
--cc=chas@locutus.cmf.nrl.navy.mil \
--cc=dhowells@redhat.com \
--cc=hch@infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@transmeta.com \
/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