| To: | Matthew Wilcox <willy@xxxxxxxxxx>, Ethan Benson <erbenson@xxxxxxxxxx> |
|---|---|
| Subject: | Re: vnodeops |
| From: | Steve Lord <lord@xxxxxxx> |
| Date: | 17 Aug 2003 08:12:59 -0500 |
| Cc: | linux-xfs@xxxxxxxxxxx |
| In-reply-to: | <20030817043704.GB10246@plato.local.lan> |
| References: | <20030817041908.GM19630@parcelfarce.linux.theplanet.co.uk> <20030817043704.GB10246@plato.local.lan> |
| Sender: | linux-xfs-bounce@xxxxxxxxxxx |
On Sat, 2003-08-16 at 23:37, Ethan Benson wrote: > On Sun, Aug 17, 2003 at 05:19:08AM +0100, Matthew Wilcox wrote: > > > > So is there any reason to keep the vnodeops layer around? There's only > > one implementation of it (xfs_vnodeops) so it seems kind of pointless. > > Removing it would probably shrink xfs quite a bit, both source and binary. > > i believe its used for CXFS. It is used by CXFS, and it also lets us keep a medium level of sanity when attempting to keep Irix and Linux versions of XFS in sync. Steve |
| <Prev in Thread] | Current Thread | [Next in Thread> |
|---|---|---|
| ||
| Previous by Date: | [PATCH] Implement immutable/append-only flags in XFS #5, Ethan Benson |
|---|---|
| Next by Date: | Re: How large file store in XFS, Nathan Scott |
| Previous by Thread: | Re: vnodeops, Ethan Benson |
| Next by Thread: | [PATCH] Implement immutable/append-only flags in XFS #5, Ethan Benson |
| Indexes: | [Date] [Thread] [Top] [All Lists] |