David Howells wrote:
> +struct netfs_io_request *new_netfs_begin_writethrough(struct kiocb *iocb,
> size_t len)
> +{
> + struct netfs_io_request *wreq = NULL;
> + struct netfs_inode *ictx = netfs_inode(file_inode(iocb->ki_filp));
> +
> + mutex_lock(&ictx->wb_lock);
> +
> + wreq =
On 28/03/2024 16:34, David Howells wrote:
The current netfslib writeback implementation creates writeback requests of
contiguous folio data and then separately tiles subrequests over the space
twice, once for the server and once for the cache. This creates a few
issues:
(1) Every time there's
...@vger.kernel.org; linux...@kvack.org; net...@vger.kernel.org; linux-
ker...@vger.kernel.org; Latchesar Ionkov ; Christian
Schoenebeck
Subject: [PATCH 19/26] netfs: New writeback implementation
The current netfslib writeback implementation creates writeback requests of
contiguous folio data and then
.ozlabs.org;
> linux-
> fsde...@vger.kernel.org; linux...@kvack.org; net...@vger.kernel.org; linux-
> ker...@vger.kernel.org; Latchesar Ionkov ; Christian
> Schoenebeck
> Subject: [PATCH 19/26] netfs: New writeback implementation
>
> The current netfslib writeback implemen
The current netfslib writeback implementation creates writeback requests of
contiguous folio data and then separately tiles subrequests over the space
twice, once for the server and once for the cache. This creates a few
issues:
(1) Every time there's a discontiguity or a change between writing
