Hello Pradeep,
> For past two months, I have been working on developing a
> log-structured file system (LFS) that supports snapshots as a part o
We are also developing an LFS for Linux 2.6, named Nilfs (a new
implementation of a log-structured file system). We implemented Nilfs
using modern tech
Andrew Morton wrote:
So I have this very old patch sitting in my todo folder. Has it moved forward
at all?
Roman Zippel didn't agree with such an implementation and created
another version which is the only proper one as he says (despite it's
less functional). Well, i am waiting for it to
On Aug 29, 2005 18:40 +0100, Matthew Wilcox wrote:
> journal_commit_transaction() is still 650+ lines long and contains 16
> local variables. By moving phase 3 into its own function, we reduce
> its length by 150+ lines and reduce it to 5 local variables.
>
> @@ -251,6 +424,7 @@ void journal_comm
vs will respond at the end of the week, he is out at the moment.
Thanks for patch Charles,
Hans
-
To unsubscribe from this list: send the line "unsubscribe linux-fsdevel" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at http://vger.kernel.org/majordomo-info.html
> Fair enough, where in /sys should such things go? /proc/fs is a
> well-known place, but there is no /sys/fs :-)
It's pretty easy to create. I had a patch:
http://marc.theaimsgroup.com/?l=linux-fsdevel&m=110099238515110&w=2
to which Greg had a comment:
http://marc.theaimsgroup.com/
må den 29.08.2005 Klokka 12:16 (-0500) skreiv Steve French:
> NFS is the only place that sets NOCMTIME on inodes in its fhget routine
> IIRC.
>
> What is the exact intent of this? Does it stay set (so mtime and ctime
> updates are never sent to the server) or does it get reset somewhere (I
> d
> NFS is the only place that sets NOCMTIME on inodes in its fhget routine
> IIRC.
FUSE too.
> What is the exact intent of this? Does it stay set (so mtime and ctime
> updates are never sent to the server) or does it get reset somewhere (I
> did not see where nfs turned it off so presumably ev
On Sun, Aug 28, 2005 at 03:48:26PM -0700, Greg KH wrote:
> No new subsystems or code shall add /proc files that do not explicitly
> pertain to process information.
Fair enough, where in /sys should such things go? /proc/fs is a
well-known place, but there is no /sys/fs :-)
Joel
--
"So
journal_commit_transaction() is still 650+ lines long and contains 16
local variables. By moving phase 3 into its own function, we reduce
its length by 150+ lines and reduce it to 5 local variables.
Signed-off-by: Matthew Wilcox <[EMAIL PROTECTED]>
commit.c | 367 +
NFS is the only place that sets NOCMTIME on inodes in its fhget routine
IIRC.
What is the exact intent of this? Does it stay set (so mtime and ctime
updates are never sent to the server) or does it get reset somewhere (I
did not see where nfs turned it off so presumably even explicit sets of
On Thu, Aug 25, 2005 at 10:45:42AM -0700, Mark Fasheh wrote:
> On Thu, Aug 25, 2005 at 11:58:19AM +0200, Christoph Hellwig wrote:
> > > > - there's still some procfs abuse
> > >
> > > Specifics of what is abuse vs OK would be interesting.
> >
> > You're using procfs for non-process data.
>
>
On Thu, Aug 25, 2005 at 10:43:05AM -0500, Brian King wrote:
> Sonny Rao wrote:
> > On Thu, Aug 25, 2005 at 03:11:03PM +0100, Brian King wrote:
> >
> >>I think this is a libsysfs/iprutils issue due to a sysfs change in
> >>recent kernels. Install sysfsutils 1.3.0, then grab the latest iprutils
>
12 matches
Mail list logo
