[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <Pine.LNX.4.64.0706201427270.31425@schroedinger.engr.sgi.com>
Date: Wed, 20 Jun 2007 14:29:21 -0700 (PDT)
From: Christoph Lameter <clameter@....com>
To: Andreas Dilger <adilger@...sterfs.com>
cc: linux-fsdevel@...r.kernel.org, linux-kernel@...r.kernel.org,
Christoph Hellwig <hch@....de>, Mel Gorman <mel@...net.ie>,
William Lee Irwin III <wli@...omorphy.com>,
David Chinner <dgc@....com>,
Jens Axboe <jens.axboe@...cle.com>,
Badari Pulavarty <pbadari@...il.com>,
Maxim Levitsky <maximlevitsky@...il.com>
Subject: Re: [34/37] Large blocksize support in ramfs
On Wed, 20 Jun 2007, Andreas Dilger wrote:
> On Jun 20, 2007 11:29 -0700, clameter@....com wrote:
> > If you apply this patch and then you can f.e. try this:
> >
> > mount -tramfs -o10 none /media
>
> > @@ -164,10 +165,15 @@ static int ramfs_fill_super(struct super
> > + if (options && *options)
> > + order = simple_strtoul(options, NULL, 10);
>
> This is probably a bad name for a mount option. What about "order=10"?
> Otherwise you prevent any other option from being used in the future.
I tried to make it as simple as possible. The patch is primarily useful as
a debugging aid since it eliminates the lower layers from the game. I
think ramfs should be left as is sine it is intended as a minimal
implementation that should stay simpl.
If we really want such an option for good then it may best be added to
shmem or ramdisk drivers?
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists