Linux-Fsdevel Archive mirror
 help / color / mirror / Atom feed
From: Bill O'Donnell <bodonnel@redhat.com>
To: Johannes Thumshirn <jth@kernel.org>
Cc: Damien Le Moal <dlemoal@kernel.org>,
	linux-fsdevel@vger.kernel.org,
	Matthew Wilcox <willy@infradead.org>,
	Johannes Thumshirn <johannes.thumshirn@wdc.com>
Subject: Re: [PATCH] zonefs: enable support for large folios
Date: Tue, 14 May 2024 14:06:51 -0500	[thread overview]
Message-ID: <ZkO2S3XiGDrTVrmi@redhat.com> (raw)
In-Reply-To: <20240513223718.29657-1-jth@kernel.org>

On Tue, May 14, 2024 at 12:37:18AM +0200, Johannes Thumshirn wrote:
> From: Johannes Thumshirn <johannes.thumshirn@wdc.com>
> 
> Enable large folio support on zonefs.
> 
> Cc: Matthew Wilcox <willy@infradead.org>
> Cc: Damien Le Moal <dlemoal@kernel.org>
> Signed-off-by: Johannes Thumshirn <johannes.thumshirn@wdc.com>

Looks fine.
Reviewed-by: Bill O'Donnell <bodonnel@redhat.com>

> ---
>  fs/zonefs/super.c | 1 +
>  1 file changed, 1 insertion(+)
> 
> diff --git a/fs/zonefs/super.c b/fs/zonefs/super.c
> index 37080ec516e8..3c5b4c3a0c3e 100644
> --- a/fs/zonefs/super.c
> +++ b/fs/zonefs/super.c
> @@ -662,6 +662,7 @@ static struct inode *zonefs_get_file_inode(struct inode *dir,
>  	inode->i_op = &zonefs_file_inode_operations;
>  	inode->i_fop = &zonefs_file_operations;
>  	inode->i_mapping->a_ops = &zonefs_file_aops;
> +	mapping_set_large_folios(inode->i_mapping);
>  
>  	/* Update the inode access rights depending on the zone condition */
>  	zonefs_inode_update_mode(inode);
> -- 
> 2.35.3
> 
> 


  reply	other threads:[~2024-05-14 19:07 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-05-13 22:37 [PATCH] zonefs: enable support for large folios Johannes Thumshirn
2024-05-14 19:06 ` Bill O'Donnell [this message]
2024-05-27  4:35 ` Damien Le Moal

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=ZkO2S3XiGDrTVrmi@redhat.com \
    --to=bodonnel@redhat.com \
    --cc=dlemoal@kernel.org \
    --cc=johannes.thumshirn@wdc.com \
    --cc=jth@kernel.org \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=willy@infradead.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).