| To: | Uday Chitragar <uchitragar@xxxxxxxxxxxxx> |
|---|---|
| Subject: | Re: Sparse files in the real world |
| From: | Christoph Hellwig <hch@xxxxxxxxxxxxx> |
| Date: | Fri, 23 Jun 2006 14:37:07 +0100 |
| Cc: | mingz@xxxxxxxxxxx, jgl@xxxxxxxxxxxxxx, linux-xfs@xxxxxxxxxxx |
| In-reply-to: | <449BA0D0.2060701@plasmon.co.uk> |
| References: | <44985423.2090803@johngroves.net> <4498F93A.7050904@plasmon.co.uk> <1150896043.4123.57.camel@localhost.localdomain> <449BA0D0.2060701@plasmon.co.uk> |
| Sender: | xfs-bounce@xxxxxxxxxxx |
| User-agent: | Mutt/1.4.2.1i |
On Fri, Jun 23, 2006 at 09:05:36AM +0100, Uday Chitragar wrote: > In short, file system filter are kernel modules. They intercept every > request being processed by XFS. In the Unix world we normally call that a stackable filesystem, filter driver is the windows temrinology. There's a few subtle issues left that make implementing them correctly very hard. We're addressing those issues at the VFS level for ecryptfs currently. |
| <Prev in Thread] | Current Thread | [Next in Thread> |
|---|---|---|
| ||
| Previous by Date: | Re: Sparse files in the real world, Ming Zhang |
|---|---|
| Next by Date: | error xlog_recover_do_inode_trans(1) / bug when recovering, Johannes Berg |
| Previous by Thread: | Re: Sparse files in the real world, Ming Zhang |
| Next by Thread: | TAKE 904196 - cleanups from Alexey, Nathan Scott |
| Indexes: | [Date] [Thread] [Top] [All Lists] |