From: "Darrick J. Wong" <djwong@kernel.org>
To: Christoph Hellwig <hch@lst.de>
Cc: Chandan Babu R <chandan.babu@oracle.com>,
Hugh Dickins <hughd@google.com>,
Andrew Morton <akpm@linux-foundation.org>,
linux-xfs@vger.kernel.org, linux-mm@kvack.org
Subject: Re: [PATCH 15/15] xfs: use xfile_get_page and xfile_put_page in xfile_obj_load
Date: Wed, 3 Jan 2024 16:21:05 -0800 [thread overview]
Message-ID: <20240104002105.GI361584@frogsfrogsfrogs> (raw)
In-Reply-To: <20240103084126.513354-16-hch@lst.de>
On Wed, Jan 03, 2024 at 08:41:26AM +0000, Christoph Hellwig wrote:
> Switch xfile_obj_load to use xfile_get_page and xfile_put_page to access
> the shmem page cache. The former uses shmem_get_folio(..., SGP_READ),
> which returns a NULL folio for a hole instead of allocating one to
> optimize the case where the caller is reading from a whole and doesn't
> want to a zeroed folio to the page cache.
>
> Signed-off-by: Christoph Hellwig <hch@lst.de>
> ---
> fs/xfs/scrub/xfile.c | 51 +++++++++++---------------------------------
> 1 file changed, 12 insertions(+), 39 deletions(-)
>
> diff --git a/fs/xfs/scrub/xfile.c b/fs/xfs/scrub/xfile.c
> index 987b03df241b02..3f9e416376d2f7 100644
> --- a/fs/xfs/scrub/xfile.c
> +++ b/fs/xfs/scrub/xfile.c
> @@ -34,13 +34,6 @@
> * xfiles assume that the caller will handle all required concurrency
> * management; standard vfs locks (freezer and inode) are not taken. Reads
> * and writes are satisfied directly from the page cache.
> - *
> - * NOTE: The current shmemfs implementation has a quirk that in-kernel reads
> - * of a hole cause a page to be mapped into the file. If you are going to
> - * create a sparse xfile, please be careful about reading from uninitialized
> - * parts of the file. These pages are !Uptodate and will eventually be
> - * reclaimed if not written, but in the short term this boosts memory
> - * consumption.
Awright, this goes away finally!
Reviewed-by: Darrick J. Wong <djwong@kernel.org>
--D
> */
>
> /*
> @@ -117,58 +110,38 @@ xfile_obj_load(
> size_t count,
> loff_t pos)
> {
> - struct inode *inode = file_inode(xf->file);
> - struct address_space *mapping = inode->i_mapping;
> - struct page *page = NULL;
> - unsigned int pflags;
> - int error = 0;
> -
> if (count > MAX_RW_COUNT)
> return -ENOMEM;
> - if (inode->i_sb->s_maxbytes - pos < count)
> + if (file_inode(xf->file)->i_sb->s_maxbytes - pos < count)
> return -ENOMEM;
>
> trace_xfile_obj_load(xf, pos, count);
>
> - pflags = memalloc_nofs_save();
> while (count > 0) {
> + struct page *page;
> unsigned int len;
>
> len = min_t(ssize_t, count, PAGE_SIZE - offset_in_page(pos));
> -
> - /*
> - * In-kernel reads of a shmem file cause it to allocate a page
> - * if the mapping shows a hole. Therefore, if we hit ENOMEM
> - * we can continue by zeroing the caller's buffer.
> - */
> - page = shmem_read_mapping_page_gfp(mapping, pos >> PAGE_SHIFT,
> - __GFP_NOWARN);
> - if (IS_ERR(page)) {
> - error = PTR_ERR(page);
> - if (error != -ENOMEM) {
> - error = -ENOMEM;
> - break;
> - }
> -
> + page = xfile_get_page(xf, pos, len, 0);
> + if (IS_ERR(page))
> + return -ENOMEM;
> + if (!page) {
> + /*
> + * No data stored at this offset, just zero the output
> + * buffer.
> + */
> memset(buf, 0, len);
> goto advance;
> }
> -
> - /*
> - * xfile pages must never be mapped into userspace, so
> - * we skip the dcache flush.
> - */
> memcpy(buf, page_address(page) + offset_in_page(pos), len);
> - put_page(page);
> -
> + xfile_put_page(xf, page);
> advance:
> count -= len;
> pos += len;
> buf += len;
> }
> - memalloc_nofs_restore(pflags);
>
> - return error;
> + return 0;
> }
>
> /*
> --
> 2.39.2
>
>
next prev parent reply other threads:[~2024-01-04 0:21 UTC|newest]
Thread overview: 41+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-03 8:41 put the xfs xfile abstraction on a diet Christoph Hellwig
2024-01-03 8:41 ` [PATCH 01/15] shmem: move the shmem_mapping assert into shmem_get_folio_gfp Christoph Hellwig
2024-01-03 23:32 ` Darrick J. Wong
2024-01-03 8:41 ` [PATCH 02/15] shmem: export shmem_get_folio Christoph Hellwig
2024-01-03 8:41 ` [PATCH 03/15] shmem: document how to "persist" data when using shmem_*file_setup Christoph Hellwig
2024-01-04 0:21 ` Darrick J. Wong
2024-01-03 8:41 ` [PATCH 04/15] xfs: remove xfile_stat Christoph Hellwig
2024-01-03 23:45 ` Darrick J. Wong
2024-01-04 6:14 ` Christoph Hellwig
2024-01-04 6:55 ` Darrick J. Wong
2024-01-03 8:41 ` [PATCH 05/15] xfs: remove the xfile_pread/pwrite APIs Christoph Hellwig
2024-01-03 23:48 ` Darrick J. Wong
2024-01-04 6:15 ` Christoph Hellwig
2024-01-04 6:58 ` Darrick J. Wong
2024-01-03 8:41 ` [PATCH 06/15] xfs: don't try to handle non-update pages in xfile_obj_load Christoph Hellwig
2024-01-03 23:55 ` Darrick J. Wong
2024-01-04 6:21 ` Christoph Hellwig
2024-01-03 8:41 ` [PATCH 07/15] xfs: shmem_file_setup can't return NULL Christoph Hellwig
2024-01-03 23:56 ` Darrick J. Wong
2024-01-03 8:41 ` [PATCH 08/15] xfs: don't modify file and inode flags for shmem files Christoph Hellwig
2024-01-04 0:01 ` Darrick J. Wong
2024-01-04 6:23 ` Christoph Hellwig
2024-01-03 8:41 ` [PATCH 09/15] xfs: don't allow highmem pages in xfile mappings Christoph Hellwig
[not found] ` <20240104000324.GC361584@frogsfrogsfrogs>
2024-01-04 6:24 ` Christoph Hellwig
2024-01-04 7:01 ` Darrick J. Wong
2024-01-03 8:41 ` [PATCH 10/15] xfs: remove xfarray_sortinfo.page_kaddr Christoph Hellwig
2024-01-04 0:04 ` Darrick J. Wong
2024-01-03 8:41 ` [PATCH 11/15] xfs: use shmem_get_folio in xfile_get_page Christoph Hellwig
2024-01-04 0:12 ` Darrick J. Wong
2024-01-04 6:25 ` Christoph Hellwig
2024-01-03 8:41 ` [PATCH 12/15] xfs: remove struct xfile_page Christoph Hellwig
2024-01-10 22:42 ` Darrick J. Wong
2024-01-03 8:41 ` [PATCH 13/15] xfs: don't unconditionally allocate a new page in xfile_get_page Christoph Hellwig
2024-01-04 0:18 ` Darrick J. Wong
2024-01-03 8:41 ` [PATCH 14/15] xfs: use xfile_get_page and xfile_put_page in xfile_obj_store Christoph Hellwig
2024-01-04 0:20 ` Darrick J. Wong
2024-01-04 6:26 ` Christoph Hellwig
2024-01-03 8:41 ` [PATCH 15/15] xfs: use xfile_get_page and xfile_put_page in xfile_obj_load Christoph Hellwig
2024-01-04 0:21 ` Darrick J. Wong [this message]
2024-01-04 1:35 ` put the xfs xfile abstraction on a diet Darrick J. Wong
2024-01-04 6:26 ` Christoph Hellwig
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20240104002105.GI361584@frogsfrogsfrogs \
--to=djwong@kernel.org \
--cc=akpm@linux-foundation.org \
--cc=chandan.babu@oracle.com \
--cc=hch@lst.de \
--cc=hughd@google.com \
--cc=linux-mm@kvack.org \
--cc=linux-xfs@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox