From: Mike Snitzer <snitzer@redhat.com>
To: Mikulas Patocka <mpatocka@redhat.com>
Cc: dm-devel@redhat.com, "Alasdair G. Kergon" <agk@redhat.com>
Subject: Re: [PATCH 6/6] dm-snapshot: use bufio prefetch
Date: Tue, 14 Jan 2014 11:58:40 -0500 [thread overview]
Message-ID: <20140114165840.GA10687@redhat.com> (raw)
In-Reply-To: <alpine.LRH.2.02.1401131914270.30362@file01.intranet.prod.int.rdu2.redhat.com>
On Mon, Jan 13 2014 at 7:14pm -0500,
Mikulas Patocka <mpatocka@redhat.com> wrote:
> This patch modifies dm-snapshot so that it prefetches the buffers when
> loading the exceptions.
>
> The number of buffers read ahead is specified in the DM_PREFETCH_CHUNKS
> macro.
>
> Signed-off-by: Mikulas Patocka <mpatocka@redhat.com>
>
> ---
> drivers/md/dm-snap-persistent.c | 22 +++++++++++++++++++++-
> 1 file changed, 21 insertions(+), 1 deletion(-)
>
> Index: linux-3.13-rc7/drivers/md/dm-snap-persistent.c
> ===================================================================
> --- linux-3.13-rc7.orig/drivers/md/dm-snap-persistent.c 2014-01-14 00:54:52.000000000 +0100
> +++ linux-3.13-rc7/drivers/md/dm-snap-persistent.c 2014-01-14 00:56:39.000000000 +0100
> @@ -18,6 +18,8 @@
> #define DM_MSG_PREFIX "persistent snapshot"
> #define DM_CHUNK_SIZE_DEFAULT_SECTORS 32 /* 16KB */
>
> +#define DM_PREFETCH_CHUNKS 12
> +
> /*-----------------------------------------------------------------
> * Persistent snapshots, by persistent we mean that the snapshot
> * will survive a reboot.
...
> @@ -504,6 +507,8 @@ static int read_exceptions(struct pstore
> if (IS_ERR(client))
> return PTR_ERR(client);
>
> + dm_bufio_set_minimum_buffers(client, DM_PREFETCH_CHUNKS + 1);
> +
Why the +1? I'd prefer that be managed in dm-bufio rather than relying
on all callers to know to add +1.
Can you supply a followup patch that cleans this up in bufio and remove
the +1 in the above dm_bufio_set_minimum_buffers call?
next prev parent reply other threads:[~2014-01-14 16:58 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-01-14 0:12 [PATCH 1/6] dm-bufio: introduce dm_bufio_forget Mikulas Patocka
2014-01-14 0:13 ` [PATCH 2/6] dm-bufio: introduce dm_bufio_set_minimum_buffers Mikulas Patocka
2014-01-14 0:13 ` [PATCH 3/6] dm-snapshot: use GFP_KERNEL when initializing the snapshot Mikulas Patocka
2014-01-14 0:14 ` [PATCH 4/6] dm-snapshot: make ps->area explicit Mikulas Patocka
2014-01-14 0:14 ` [PATCH 5/6] dm-snapshot: use dm-bufio Mikulas Patocka
2014-01-14 0:14 ` [PATCH 6/6] dm-snapshot: use bufio prefetch Mikulas Patocka
2014-01-14 16:58 ` Mike Snitzer [this message]
2014-01-14 20:43 ` Mikulas Patocka
2014-01-14 21:50 ` Mike Snitzer
2014-01-16 20:53 ` Mikulas Patocka
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=20140114165840.GA10687@redhat.com \
--to=snitzer@redhat.com \
--cc=agk@redhat.com \
--cc=dm-devel@redhat.com \
--cc=mpatocka@redhat.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.