From: David Howells <dhowells@warthog.cambridge.redhat.com>
To: Jeff Garzik <jgarzik@pobox.com>
Cc: Christoph Hellwig <hch@infradead.org>,
David Howells <dhowells@redhat.com>,
torvalds@transmeta.com, linux-kernel@vger.kernel.org,
linux-fsdevel@vger.kernel.org, openafs-devel@openafs.org
Subject: Re: [PATCH] in-core AFS multiplexor and PAG support
Date: Tue, 13 May 2003 17:57:47 +0100 [thread overview]
Message-ID: <9068.1052845067@warthog.warthog> (raw)
In-Reply-To: <20030513163929.GB30944@gtf.org>
> AFS is annoying and painful no matter how you look at it. :/
>
> But I don't think 90+ new syscalls is the answer, even for 2.7.
I think it's going to be either
(1) try to maintain compatibility with OpenAFS and Arla's current syscall
setup
(2) totally rewrite the interface and tell OpenAFS/Arla they have to change
too.
In the case of (2), I think the AFS operations would best be emulated by a
combination of the following means:
(1) Use the setpag() syscall in my patch.
(2) Add syscalls for managing tokens on a general filesystem-by-filesystem
basis (only need four ops: set, get, delete and clear-all). These could
work through operations in struct file_system_type.
(3) Work through sysfs files for fs-specific control functions. Things like
adding cells would come into this category.
(4) Emulate as much as many of the inode-requiring pioctl calls as possible
with xattr syscalls.
However, this leaves at least one that doesn't fit into any of the above
categories. VIOC_STAT_MT_PT takes an inode, and so should come into (4) except
that the xattr key size isn't sufficiently capacious.
There are two ways to deal with this:
(1) Add an actual pioctl syscall as a top-level syscall and make it either
call a pioctl method in inode_operations or maybe have it fake a dentry
and file and call file_operations->ioctl.
(2) Open the directory holding the mountpoint and make an ioctl that aims at
the mountpoint in question.
David
next prev parent reply other threads:[~2003-05-13 16:57 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-05-13 15:39 [PATCH] in-core AFS multiplexor and PAG support David Howells
2003-05-13 15:52 ` Linus Torvalds
2003-05-13 15:44 ` Alan Cox
2003-05-13 16:52 ` Jan Harkes
2003-05-13 16:57 ` Linus Torvalds
2003-05-13 16:39 ` Alan Cox
2003-05-13 21:46 ` Russ Allbery
2003-05-16 15:38 ` [OpenAFS-devel] " Derek Atkins
2003-05-13 16:05 ` David Howells
2003-05-13 16:24 ` Douglas E. Engert
2003-05-13 16:47 ` Linus Torvalds
2003-05-13 17:20 ` Jan Harkes
2003-05-13 18:21 ` David Howells
2003-05-13 18:51 ` Douglas E. Engert
2003-05-13 20:33 ` [OpenAFS-devel] " Jan Harkes
2003-05-13 21:26 ` Douglas E. Engert
2003-05-13 21:40 ` [OpenAFS-devel] " Jan Harkes
2003-05-13 22:14 ` Douglas E. Engert
2003-05-14 2:02 ` Jan Harkes
2003-05-17 12:30 ` Pavel Machek
2003-05-18 14:22 ` Nathan Neulinger
2003-05-18 18:06 ` [OpenAFS-devel] " Pavel Machek
2003-05-13 17:23 ` Trond Myklebust
2003-05-15 11:41 ` Ingo Oeser
2003-05-13 17:42 ` David Howells
2003-05-13 16:03 ` Christoph Hellwig
2003-05-13 16:12 ` David Howells
2003-05-13 20:23 ` Christoph Hellwig
2003-05-13 16:39 ` Jeff Garzik
2003-05-13 16:57 ` David Howells [this message]
[not found] <20030513182950.GB30766@delft.aura.cs.cmu.edu>
2003-05-13 18:53 ` David Howells
-- strict thread matches above, loose matches on Subject: below --
2003-05-13 15:34 David Howells
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=9068.1052845067@warthog.warthog \
--to=dhowells@warthog.cambridge.redhat.com \
--cc=dhowells@redhat.com \
--cc=hch@infradead.org \
--cc=jgarzik@pobox.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=openafs-devel@openafs.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