Re: [PATCH 00/14] Pramfs: Persistent and protected ram filesystem

2009-06-21 Thread Marco Stornelli
2009/6/21 Pavel Machek : > >> >> 1. Disk-based filesystems such as ext2/ext3 were designed for optimum >> >>    performance on spinning disk media, so they implement features such >> >>    as block groups, which attempts to group inode data into a contiguous >> >>    set of data blocks to minimize

Re: [PATCH 06/14] Pramfs: Include files

2009-06-21 Thread Marco Stornelli
2009/6/21 Arnd Bergmann : > On Sunday 21 June 2009, Marco wrote: >> I was thinking about your comment and I think I'll use __kernel_off_t >> for the exported headers. I know that it will differ between 32 and 64 >> bit architectures, but for this kind of fs there isn't any compatibility >> problem

[PATCH 1/2] MMC Agressive clocking framework v4

2009-06-21 Thread Linus Walleij
This patch modified the MMC core code to optionally call the set_ios() operation on the driver with the clock frequency set to 0 to gate the hardware block clock (and thus the MCI clock) for an MMC host controller after a grace period of at least 8 MCLK cycles. It is inspired by existing clock gati

[PATCH 2/2] Modify MMCI/PL180 to handle agressive clocking v4

2009-06-21 Thread Linus Walleij
This adds a few clk_enable()/clk_disable() calls to the MMCI driver so as to handle an set_ios() request with clock frequency set to 0 as an instruction to gate the block clock. This also breaks out the clock setting code into its own function to simplify the set_ios() function a bit. Signed-off-b

Re: [PATCH 00/14] Pramfs: Persistent and protected ram filesystem

2009-06-21 Thread Pavel Machek
> >> 1. Disk-based filesystems such as ext2/ext3 were designed for optimum > >>performance on spinning disk media, so they implement features such > >>as block groups, which attempts to group inode data into a contiguous > >>set of data blocks to minimize disk seeking when accessing fi

Re: [PATCH 1/2] MMC Agressive clocking framework v3

2009-06-21 Thread Pierre Ossman
On Sun, 21 Jun 2009 22:05:18 +0200 Linus Walleij wrote: > 2009/6/18 Linus Walleij : > > > diff --git a/drivers/mmc/core/Kconfig b/drivers/mmc/core/Kconfig > >(...) > > + Of unsure, say N. > > However the rest of the patch is as I intended. I'll send a V4 pronto > if you want that for th

Re: [PATCH 06/14] Pramfs: Include files

2009-06-21 Thread Arnd Bergmann
On Sunday 21 June 2009, Marco wrote: > I was thinking about your comment and I think I'll use __kernel_off_t > for the exported headers. I know that it will differ between 32 and 64 > bit architectures, but for this kind of fs there isn't any compatibility > problem at layout level. You cannot remo

Re: [PATCH 1/2] MMC Agressive clocking framework v3

2009-06-21 Thread Linus Walleij
2009/6/18 Linus Walleij : > diff --git a/drivers/mmc/core/Kconfig b/drivers/mmc/core/Kconfig >(...) > + Of unsure, say N. However the rest of the patch is as I intended. I'll send a V4 pronto if you want that for the current merge window. Linus Walleij -- To unsubscribe from this list: s

Re: [PATCH 00/14] Pramfs: Persistent and protected ram filesystem

2009-06-21 Thread Marco
Pavel Machek wrote: >>> Why is an entire filesystem needed, instead of simply a block driver >>> if the ramdisk driver cannot be used? >>> >> >From documentation: >> >> "A relatively straight-forward solution is to write a simple block >> driver for the non-volatile RAM, and mount over it any disk-

Re: [PATCH 06/14] Pramfs: Include files

2009-06-21 Thread Marco
Arnd Bergmann wrote: > On Saturday 13 June 2009, Sam Ravnborg wrote: >>> + union { >>> + struct { >>> + /* >>> + * ptr to row block of 2D block pointer array, >>> + * file block #'s 0 to (blocksize/4)^2 - 1. >>> +