Linux Btrfs filesystem development
 help / color / mirror / Atom feed
From: Omar Sandoval <osandov@osandov.com>
To: dsterba@suse.cz, Filipe Manana <fdmanana@gmail.com>,
	David Sterba <dsterba@suse.com>,
	linux-btrfs <linux-btrfs@vger.kernel.org>
Subject: Re: [PATCH] btrfs: use kvzalloc for EXTENT_SAME temporary data
Date: Fri, 11 May 2018 10:31:50 -0700	[thread overview]
Message-ID: <20180511173150.GD29366@vader> (raw)
In-Reply-To: <20180511164916.GC6649@twin.jikos.cz>

On Fri, May 11, 2018 at 06:49:16PM +0200, David Sterba wrote:
> On Fri, May 11, 2018 at 05:25:50PM +0100, Filipe Manana wrote:
> > On Fri, May 11, 2018 at 4:57 PM, David Sterba <dsterba@suse.com> wrote:
> > > The dedupe range is 16 MiB, with 4KiB pages and 8 byte pointers, the
> > > arrays can be 32KiB large. To avoid allocation failures due to
> > > fragmented memory, use the allocation with fallback to vmalloc.
> > >
> > > Signed-off-by: David Sterba <dsterba@suse.com>
> > > ---
> > >
> > > This depends on the patches that remove the 16MiB restriction in the
> > > dedupe ioctl, but contextually can be applied to the current code too.
> > >
> > > https://patchwork.kernel.org/patch/10374941/
> > >
> > >  fs/btrfs/ioctl.c | 4 ++--
> > >  1 file changed, 2 insertions(+), 2 deletions(-)
> > >
> > > diff --git a/fs/btrfs/ioctl.c b/fs/btrfs/ioctl.c
> > > index b572e38b4b64..a7f517009cd7 100644
> > > --- a/fs/btrfs/ioctl.c
> > > +++ b/fs/btrfs/ioctl.c
> > > @@ -3178,8 +3178,8 @@ static int btrfs_extent_same(struct inode *src, u64 loff, u64 olen,
> > >          * locking. We use an array for the page pointers. Size of the array is
> > >          * bounded by len, which is in turn bounded by BTRFS_MAX_DEDUPE_LEN.
> > >          */
> > > -       cmp.src_pages = kcalloc(num_pages, sizeof(struct page *), GFP_KERNEL);
> > > -       cmp.dst_pages = kcalloc(num_pages, sizeof(struct page *), GFP_KERNEL);
> > > +       cmp.src_pages = kvzalloc(num_pages, sizeof(struct page *), GFP_KERNEL);
> > > +       cmp.dst_pages = kvzalloc(num_pages, sizeof(struct page *), GFP_KERNEL);
> > 
> > Kvzalloc should take 2 parameters and not 3.
> 
> And the right function is kvmalloc_array.
> 
> > Also, aren't the corresponding kvfree() calls missing?
> 
> Yes, thanks for catching it. The updated version:
> 
> From: David Sterba <dsterba@suse.com>
> Subject: [PATCH] btrfs: use kvzalloc for EXTENT_SAME temporary data
> 
> The dedupe range is 16 MiB, with 4KiB pages and 8 byte pointers, the
> arrays can be 32KiB large. To avoid allocation failures due to
> fragmented memory, use the allocation with fallback to vmalloc.
> 
> Signed-off-by: David Sterba <dsterba@suse.com>
> ---
>  fs/btrfs/ioctl.c | 16 +++++++++-------
>  1 file changed, 9 insertions(+), 7 deletions(-)
> 
> diff --git a/fs/btrfs/ioctl.c b/fs/btrfs/ioctl.c
> index b572e38b4b64..4fcfa05ed960 100644
> --- a/fs/btrfs/ioctl.c
> +++ b/fs/btrfs/ioctl.c
> @@ -3178,12 +3178,13 @@ static int btrfs_extent_same(struct inode *src, u64 loff, u64 olen,
>  	 * locking. We use an array for the page pointers. Size of the array is
>  	 * bounded by len, which is in turn bounded by BTRFS_MAX_DEDUPE_LEN.
>  	 */
> -	cmp.src_pages = kcalloc(num_pages, sizeof(struct page *), GFP_KERNEL);
> -	cmp.dst_pages = kcalloc(num_pages, sizeof(struct page *), GFP_KERNEL);
> +	cmp.src_pages = kvmalloc_array(num_pages, sizeof(struct page *),
> +				       GFP_KERNEL);
> +	cmp.dst_pages = kvmalloc_array(num_pages, sizeof(struct page *),
> +				       GFP_KERNEL);

kcalloc() implies __GFP_ZERO, do we need that here?

>  	if (!cmp.src_pages || !cmp.dst_pages) {
> -		kfree(cmp.src_pages);
> -		kfree(cmp.dst_pages);
> -		return -ENOMEM;
> +		ret = -ENOMEM;
> +		goto out_free;
>  	}
>  
>  	if (same_inode)
> @@ -3211,8 +3212,9 @@ static int btrfs_extent_same(struct inode *src, u64 loff, u64 olen,
>  	else
>  		btrfs_double_inode_unlock(src, dst);
>  
> -	kfree(cmp.src_pages);
> -	kfree(cmp.dst_pages);
> +out_free:
> +	kvfree(cmp.src_pages);
> +	kvfree(cmp.dst_pages);
>  
>  	return ret;
>  }
> -- 
> 2.16.2
> 
> --
> To unsubscribe from this list: send the line "unsubscribe linux-btrfs" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html

  parent reply	other threads:[~2018-05-11 17:31 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-05-11 15:57 [PATCH] btrfs: use kvzalloc for EXTENT_SAME temporary data David Sterba
2018-05-11 16:25 ` Filipe Manana
2018-05-11 16:49   ` David Sterba
2018-05-11 17:16     ` Filipe Manana
2018-05-11 21:01       ` David Sterba
2018-05-11 17:31     ` Omar Sandoval [this message]
2018-05-11 17:47       ` Timofey Titovets

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=20180511173150.GD29366@vader \
    --to=osandov@osandov.com \
    --cc=dsterba@suse.com \
    --cc=dsterba@suse.cz \
    --cc=fdmanana@gmail.com \
    --cc=linux-btrfs@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