linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Miklos Szeredi <mszeredi@inf.bme.hu>
To: hallyn@CS.WM.EDU
Cc: linux-kernel@vger.kernel.org
Subject: Re: unionfs
Date: Thu, 11 Mar 2004 16:44:07 +0100 (MET)	[thread overview]
Message-ID: <200403111544.i2BFi7O06675@kempelen.iit.bme.hu> (raw)
In-Reply-To: <20040311151343.GA943@escher.cs.wm.edu> (hallyn@CS.WM.EDU)


> If you get a response from Al, could you let me know?

OK.

> I've been wondering about this myself, and beyond simple
> coolness/usefullness, we may also need the unionfs for mls
> polyinstantiation.
> 
> If you don't hear from Al, please let me know whether you plan to tackle
> it yourself or not.

I'll have to, as this is needed for AVFS.  Not unionfs, but something
similar, that allows file/directory lookups for special filenames to
be redirected to another filesystem.

For the time I plan to go along the easy way, and create a filesystem
specifically for AVFS that doesn't need modifications to the kernel.
This will be inefficient in a number of ways: doubling the memory use
by the dentry/inode caches, deeper call chains for all filesystem
operations (even those, that require no intervention).

The next step will be to try to optimize and generalize it to be
usable for other filesystems like unionsfs.  I'd really love to have
some input about this from Al or anybody who has any ideas.

Miklos

  parent reply	other threads:[~2004-03-11 15:44 UTC|newest]

Thread overview: 35+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-03-08  9:52 unionfs Miklos Szeredi
2004-03-08 16:10 ` unionfs Bernd Schubert
2004-03-09  9:38   ` unionfs Miklos Szeredi
     [not found] ` <20040311151343.GA943@escher.cs.wm.edu>
2004-03-11 15:44   ` Miklos Szeredi [this message]
2004-03-14  2:33     ` unionfs Ian Kent
2004-03-14  4:20       ` unionfs Horst von Brand
2004-03-16 12:42       ` unionfs Miklos Szeredi
     [not found]     ` <20040315214207.GA26615@escher.cs.wm.edu>
2004-03-16 13:43       ` unionfs Miklos Szeredi
2004-03-12 23:37 ` unionfs Herbert Poetzl
2004-03-15 11:35 unionfs Carsten Otte
2004-03-15 12:19 ` unionfs Jörn Engel
2004-03-15 12:47   ` unionfs Ian Kent
2004-03-15 13:16     ` unionfs Jörn Engel
2004-03-15 14:35       ` unionfs Ian Kent
2004-03-15 16:13         ` unionfs Jörn Engel
2004-03-15 17:09           ` unionfs Claudio Martins
2004-03-15 19:22           ` unionfs Horst von Brand
2004-03-15 23:20             ` unionfs Chris Friesen
2004-03-16 16:04               ` unionfs Horst von Brand
2004-03-16 17:31                 ` unionfs Jörn Engel
2004-03-16 18:04                   ` unionfs Jörn Engel
2004-03-16 19:40                     ` unionfs Horst von Brand
2004-03-16 20:45                       ` unionfs Jörn Engel
2004-03-16 19:19                   ` unionfs Horst von Brand
2004-03-16 20:00                     ` unionfs Chris Friesen
2004-03-23  2:38                   ` unionfs Robert White
2004-03-15 23:52             ` unionfs Jörn Engel
2004-03-16 16:18               ` unionfs Horst von Brand
2004-03-16 17:10                 ` unionfs Jörn Engel
2004-03-19  9:11                   ` unionfs Jamie Lokier
2004-03-19  9:42                     ` unionfs Jörn Engel
2004-03-19  9:04                 ` unionfs Jamie Lokier
2004-03-16 19:03             ` unionfs Andy Isaacson
2004-03-15 14:37       ` unionfs Ian Kent
2004-03-15 16:15       ` unionfs Jörn Engel

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=200403111544.i2BFi7O06675@kempelen.iit.bme.hu \
    --to=mszeredi@inf.bme.hu \
    --cc=hallyn@CS.WM.EDU \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).