On Fri, 27 Jul 2012, Lukas Czerner wrote:
> Currently the allocation might happen in the punched range after the
> truncation and before the releasing the space of the range. This would
> lead to blocks being unallocated under the mapped buffer heads resulting
> in nasty bugs.
>
> With this commi
invalidatepage_range is not implemented by the caller.
>
> Signed-off-by: Lukas Czerner
> Cc: Andrew Morton
> Cc: Hugh Dickins
Needs some rework.
> ---
Documentation/filesystems/Locking
Documentation/filesystems/netfs-api.txt
Documentation/filesystems/vfs.txt
all have somethi
gt; invalidatepage_range address space operation, or rely solely on the
> block_invalidatepage_range. That said it will BUG_ON() if caller
> implements invalidatepage(), does not implement invalidatepage_range()
> and use truncate_inode_pages_range() with unaligned end of the range.
>
>
(I wonder if linux-mmc@vger.kernel.org was supposed to be
linux...@kvack.org? Our apologies to linux-mmc if so.)
On Sat, 18 Aug 2012, Theodore Ts'o wrote:
> On Fri, Jul 27, 2012 at 10:00:59AM +0200, Lukas Czerner wrote:
> > This set of patches are aimed to allow truncate_inode_pages_range() handl
On Mon, 2 Apr 2012, Luca Porzio (lporzio) wrote:
>
> Great topics. As per one of Rik original points:
>
> > 4) skip writeout of zero-filled pages - this can be a big help
> > for KVM virtual machines running Windows, since Windows zeroes
> > out free pages; simply discarding a zero-fill
On Mon, 2 Apr 2012, Arnd Bergmann wrote:
>
> Another option would be batched discard as we do it for file systems:
> occasionally stop writing to swap space and scanning for areas that
> have become available since the last discard, then send discard
> commands for those.
I'm not sure whether you
On Fri, 30 Mar 2012, Arnd Bergmann wrote:
> On Friday 30 March 2012, Arnd Bergmann wrote:
>
> We've had a discussion in the Linaro storage team (Saugata, Venkat and me,
> with Luca joining in on the discussion) about swapping to flash based media
> such as eMMC. This is a summary of what we fou
