From: David Sterba <dsterba@suse.cz>
To: Liu Bo <bo.li.liu@oracle.com>
Cc: linux-btrfs@vger.kernel.org
Subject: Re: [PATCH v2] Btrfs: add readahead for send_write
Date: Mon, 3 Mar 2014 15:25:28 +0100 [thread overview]
Message-ID: <20140303142528.GC7004@twin.jikos.cz> (raw)
In-Reply-To: <1393838683-25216-1-git-send-email-bo.li.liu@oracle.com>
On Mon, Mar 03, 2014 at 05:24:43PM +0800, Liu Bo wrote:
> --- a/fs/btrfs/send.c
> +++ b/fs/btrfs/send.c
> @@ -3972,6 +3972,7 @@ static ssize_t fill_read_buf(struct send_ctx *sctx, u64 offset, u32 len)
> pgoff_t last_index;
> unsigned pg_offset = offset & ~PAGE_CACHE_MASK;
> ssize_t ret = 0;
> + struct file_ra_state *ra = NULL;
>
> key.objectid = sctx->cur_ino;
> key.type = BTRFS_INODE_ITEM_KEY;
> @@ -3991,6 +3992,17 @@ static ssize_t fill_read_buf(struct send_ctx *sctx, u64 offset, u32 len)
> goto out;
>
> last_index = (offset + len - 1) >> PAGE_CACHE_SHIFT;
> +
> + /* initial readahead */
> + ra = kzalloc(sizeof(*ra), GFP_NOFS);
> + if (!ra) {
> + ret = -ENOMEM;
This should not be a hard failure, it can continue without RA for this
buffer. Besides, the RA buffer can be allocated at the beginning of send
operation and pointer stored in the send context.
> + goto out;
> + }
> +
> + file_ra_state_init(ra, inode->i_mapping);
> + btrfs_force_ra(inode->i_mapping, ra, NULL, index, last_index-index + 1);
> +
> while (index <= last_index) {
> unsigned cur_len = min_t(unsigned, len,
> PAGE_CACHE_SIZE - pg_offset);
> @@ -4022,6 +4034,7 @@ static ssize_t fill_read_buf(struct send_ctx *sctx, u64 offset, u32 len)
> ret += cur_len;
> }
> out:
> + kfree(ra);
> iput(inode);
> return ret;
> }
> --
> 1.8.1.4
>
> --
> 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
next prev parent reply other threads:[~2014-03-03 14:25 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-03-03 9:24 [PATCH v2] Btrfs: add readahead for send_write Liu Bo
2014-03-03 14:25 ` David Sterba [this message]
2014-03-04 2:49 ` Liu Bo
2014-03-04 12:31 ` 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=20140303142528.GC7004@twin.jikos.cz \
--to=dsterba@suse.cz \
--cc=bo.li.liu@oracle.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