From: Anand Jain <anand.jain@oracle.com>
To: Nikolay Borisov <nborisov@suse.com>, linux-btrfs@vger.kernel.org
Subject: Re: [PATCH] btrfs: Document parameters of btrfs_reserve_extent
Date: Tue, 13 Mar 2018 21:56:23 +0800 [thread overview]
Message-ID: <21852f3c-f330-ecc8-543d-62c0cc4b66bb@oracle.com> (raw)
In-Reply-To: <1520936552-11586-1-git-send-email-nborisov@suse.com>
On 03/13/2018 06:22 PM, Nikolay Borisov wrote:
> This function is the entry to the extent allocator and as such has
> quite a number of parameters. Some of those have subtle effects on the
> allocation algorithm. Document the parameters.
>
> Signed-off-by: Nikolay Borisov <nborisov@suse.com>
Reviewed-by: Anand Jain <anand.jain@oracle.com>
> ---
> fs/btrfs/extent-tree.c | 45 +++++++++++++++++++++++++++++++++++++++++++++
> 1 file changed, 45 insertions(+)
>
> diff --git a/fs/btrfs/extent-tree.c b/fs/btrfs/extent-tree.c
> index bb1861033071..60ece25101ee 100644
> --- a/fs/btrfs/extent-tree.c
> +++ b/fs/btrfs/extent-tree.c
> @@ -7961,6 +7961,51 @@ static void dump_space_info(struct btrfs_fs_info *fs_info,
> up_read(&info->groups_sem);
> }
>
> +/*
> + * btrfs_reserve_extent - entry point to the extent allocator. Tries to find a
> + * hole that is at least as big as @num_bytes.
> + *
> + * @root - The root that will contains this extent
> + *
> + * @ram_bytes - The amount of space in ram that @num_bytes take. This
> + * is used for accounting purposes. This value differs
> + * than @num_bytes only in the case of compressed extents.
> + *
> + * @num_bytes - Number of bytes to allocates on-disk.
> + *
> + * @min_alloc_size - Indicates the minimum amount of memory that the
> + * allocator should try to satisfy. In some cases
> + * @num_bytes may be larger than what is required and if
> + * the filesystem is fragmented then allocation fails.
> + * However, the presence of @min_alloc_size gives a
> + * chance to try and satisfy the smaller allocation.
> + *
> + * @empty_size - A hint that you plan on doing more cow. This is the
> + * size in bytes the allocator should try to find free
> + * next to the block it returns. This is just a hint and
> + * may be ignored by the allocator.
> + *
> + * @hint_byte - Hint to the allocator to start searching above the byte
> + * address passed. It might be ignored.
> + *
> + * @ins - This key is modified to record the found hole. It will
> + * have the following values:
> + * ins->objectid == start position
> + * ins->flags = BTRFS_EXTENT_ITEM_KEY
> + * ins->offset == the size of the hole.
> + *
> + * @is_data - Boolean flag indicating whether an extent is
> + * allocated for data (true) or metadata (false)
> + *
> + * @delalloc - Boolean flag indicating whether this allocation is for
> + * delalloc or not. If 'true' data_rwsem of block groups
> + * is going to be acquired.
> + *
> + *
> + * Returns 0 when an allocation succeeded or < 0 when an error occurred. In
> + * case -ENOSPC is returned then @ins->offset will contain the size of the
> + * largest available hole the allocator managed to find.
> + */
> int btrfs_reserve_extent(struct btrfs_root *root, u64 ram_bytes,
> u64 num_bytes, u64 min_alloc_size,
> u64 empty_size, u64 hint_byte,
>
next prev parent reply other threads:[~2018-03-13 13:54 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-03-13 10:22 [PATCH] btrfs: Document parameters of btrfs_reserve_extent Nikolay Borisov
2018-03-13 13:56 ` Anand Jain [this message]
2018-03-14 20:08 ` David Sterba
2018-03-16 18:43 ` Liu Bo
2018-03-16 18:44 ` Nikolay Borisov
2018-03-16 19:41 ` David Sterba
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=21852f3c-f330-ecc8-543d-62c0cc4b66bb@oracle.com \
--to=anand.jain@oracle.com \
--cc=linux-btrfs@vger.kernel.org \
--cc=nborisov@suse.com \
/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 NNTP newsgroup(s).