From: Alasdair G Kergon <agk@redhat.com>
To: device-mapper development <dm-devel@redhat.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [dm-devel] [PATCH] dm: noflush resizing (0/3)
Date: Fri, 26 Oct 2007 01:37:53 +0100 [thread overview]
Message-ID: <20071026003753.GO10006@agk.fab.redhat.com> (raw)
In-Reply-To: <4720E479.4020906@ce.jp.nec.com>
On Thu, Oct 25, 2007 at 02:46:17PM -0400, Jun'ichi Nomura wrote:
> So as far as I understand, the point is:
> 1. it's preferable to resize inode after the resume, if possible
Not quite - I'm not expressing a preference yet.
I'm saying the patches you presented were one option to resolve the
problem, but it was not obvious to me they are the only option and I
wanted to see a deeper analysis (keeping in mind the general direction
I want the device-mapper code to be heading in).
In other words, an analysis that draws out the conflict at the heart of
this problem, and whether the problem we have with this locking is
intrinsic to the current design or just a matter of implementation that
can be fixed with some re-ordering or tweaks to the usage rules or types
of the locks.
Alasdair
--
agk@redhat.com
prev parent reply other threads:[~2007-10-26 0:38 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-10-24 21:25 [PATCH] dm: noflush resizing (0/3) Jun'ichi Nomura
2007-10-25 1:24 ` [dm-devel] " Alasdair G Kergon
2007-10-25 14:18 ` Jun'ichi Nomura
2007-10-25 14:48 ` Alasdair G Kergon
2007-10-25 18:46 ` Jun'ichi Nomura
2007-10-25 23:51 ` Jun'ichi Nomura
2007-10-26 0:37 ` Alasdair G Kergon [this message]
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=20071026003753.GO10006@agk.fab.redhat.com \
--to=agk@redhat.com \
--cc=dm-devel@redhat.com \
--cc=linux-kernel@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