From: Daniel Phillips <phillips@phunq.net>
To: FUJITA Tomonori <fujita.tomonori@lab.ntt.co.jp>
Cc: dm-devel@redhat.com, agk@redhat.com
Subject: Re: [PATCH RFC] dm snapshot: shared exception store
Date: Tue, 12 Aug 2008 17:28:21 -0700 [thread overview]
Message-ID: <200808121728.22025.phillips@phunq.net> (raw)
In-Reply-To: <20080813082953F.fujita.tomonori@lab.ntt.co.jp>
On Tuesday 12 August 2008 16:29, FUJITA Tomonori wrote:
> On Wed, 13 Aug 2008 08:24:41 +0900
> FUJITA Tomonori <fujita.tomonori@lab.ntt.co.jp> wrote:
>
> > On Tue, 12 Aug 2008 12:00:36 -0700
> > Daniel Phillips <phillips@phunq.net> wrote:
> >
> > > On Tuesday 12 August 2008 06:14, FUJITA Tomonori wrote:
> > > > > You just want to use getblk for alloc_chunk_buffer,
> > > > > not vmalloc.
> > > >
> > > > I think that it means that we cache all the chunks, both btree chunks
> > > > and the data chunks (which are passed to the upper layer such as file
> > > > systems). I think that we don't want cache the latter in dm.
> > >
> > > That is true. However your code should not be reading data chunks into
> > > memory at all. The only time the snapshot code has to read a data
> > > chunk is when performing the copy from origin to snapshot store in
> > > make_unique. Your code does not directly perform this task as far as I
> > > can see. That would be done in a part of the dm snapshot code your
> > > patch does not touch, which I seem to recall uses the kcopyd mechanism.
> >
> > Yes, dm-snapshot doesn't access to data chunks. However, dm does for
> > dm-snapshot (by using submit_bio friends). So if dm-snapshot uses
> > __getblk, we use both __getblk and submit_bio with a single device at
> > the same time. I think that it's the right thing.
>
> Oops, I meant, I don't think that it's the right thing.
Sure, it is perfectly ok.
Regards,
Daniel
next prev parent reply other threads:[~2008-08-13 0:28 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-08-04 8:22 [PATCH RFC] dm snapshot: shared exception store FUJITA Tomonori
2008-08-06 19:14 ` Mikulas Patocka
2008-08-09 5:01 ` FUJITA Tomonori
2008-08-11 22:12 ` Mikulas Patocka
2008-08-11 23:34 ` FUJITA Tomonori
2008-08-12 0:15 ` Steve VanDeBogart
2008-08-12 12:30 ` Daniel Phillips
2008-08-14 0:14 ` Daniel Phillips
2008-08-15 8:17 ` FUJITA Tomonori
2008-08-15 8:43 ` Daniel Phillips
2008-08-15 9:25 ` FUJITA Tomonori
2008-08-16 20:14 ` Daniel Phillips
2008-08-15 13:53 ` Ryusuke Konishi
2008-08-12 12:56 ` Daniel Phillips
2008-08-12 13:14 ` FUJITA Tomonori
2008-08-12 19:00 ` Daniel Phillips
2008-08-12 23:24 ` FUJITA Tomonori
2008-08-12 23:29 ` FUJITA Tomonori
2008-08-13 0:28 ` Daniel Phillips [this message]
2008-08-12 19:07 ` Daniel Phillips
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=200808121728.22025.phillips@phunq.net \
--to=phillips@phunq.net \
--cc=agk@redhat.com \
--cc=dm-devel@redhat.com \
--cc=fujita.tomonori@lab.ntt.co.jp \
/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.