public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: David Teigland <teigland@redhat.com>
To: Jan Hudec <bulb@ucw.cz>
Cc: Al Viro <viro@ftp.linux.org.uk>,
	linux-kernel@vger.kernel.org, akpm@osdl.org,
	linux-fsdevel@vger.kernel.org
Subject: Re: [PATCH 11/16] GFS: mount and tuning options
Date: Wed, 12 Oct 2005 11:12:56 -0500	[thread overview]
Message-ID: <20051012161256.GA9058@redhat.com> (raw)
In-Reply-To: <20051012084323.GC21612@djinn>

On Wed, Oct 12, 2005 at 10:43:24AM +0200, Jan Hudec wrote:
> They are normal directories and normal files, except they are not
> exposed in the mount-point, right? Then why don't you simply provide a
> directory handle for the master directory and use normal filesystem
> operations for the rest?
> 
> That way you would have just one ioctl -- getmasterdir. The tool would
> fchdir to the handle returned and manipulate the files from there with
> normal syscalls. It would still see to the user-visible part throught
> the root directory too (since bind mounts are supported, this should not
> be a problem).

That sounds nice, we'll give it a try.

> Well, if you get rid of the access to files in the master directory by
> making that directory visible somehow, you will be left with a bunch of
> ioctls on files, which are different enough to warrant individual ioctl
> numbers for sake of efficiency.

Sure, that may well be saner when we get the ioctl command set further
reduced.

Thanks,
Dave


      reply	other threads:[~2005-10-12 16:13 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-10-10 17:10 [PATCH 11/16] GFS: mount and tuning options David Teigland
2005-10-10 21:01 ` Greg KH
2005-10-10 21:14   ` David Teigland
2005-10-10 21:19     ` Greg KH
2005-10-10 21:30       ` Al Viro
2005-10-10 22:22         ` David Teigland
2005-10-10 21:37 ` Al Viro
2005-10-11 21:38   ` David Teigland
2005-10-12  8:43     ` Jan Hudec
2005-10-12 16:12       ` David Teigland [this message]

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=20051012161256.GA9058@redhat.com \
    --to=teigland@redhat.com \
    --cc=akpm@osdl.org \
    --cc=bulb@ucw.cz \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=viro@ftp.linux.org.uk \
    /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