From: Joe Thornber <thornber@redhat.com>
To: Mike Snitzer <snitzer@redhat.com>
Cc: dm-devel@redhat.com, ejt@redhat.com
Subject: Re: dm thin: relax hard limit on the maximum size of a metadata device
Date: Tue, 6 Mar 2012 10:09:53 +0000 [thread overview]
Message-ID: <20120306100952.GA5323@ubuntu> (raw)
In-Reply-To: <20120305140421.GA25562@redhat.com>
On Mon, Mar 05, 2012 at 09:04:21AM -0500, Mike Snitzer wrote:
> On Mon, Mar 05 2012 at 5:21am -0500,
> Joe Thornber <thornber@redhat.com> wrote:
>
> > Hi Mike,
> >
> > My concerns are:
> >
> > i) The current behaviour is upstream; by changing this aren't you
> > making the tools writers life more complicated rather than less by
> > making them support both interfaces?
>
> It is an incremental improvement. Allows the kernel to be forgiving.
> How does this impact some tool that took the special care to limit the
> size of the device to METADATA_DEV_MAX_SECTORS (which is < 16G)?
You're making this change to make life easier for tool writers, yet
tool writers still have to support the existing 3.2 kernel and deal
with the 16G limit.
> Whatever the tools may be doing is not my concern. Ideally the users
> and tool authors understand that 16G is insane for thinp metadata. But
> in the event that they use 16G would you rather we reject them?
Yes, I would rather reject, than let people think they had 32G of
metadata. It also forces the tool writers to do something sane.
I don't feel strongly enough about this to keep arguing. So consider
this an ACK and see if you can get it past Alasdair.
- Joe
prev parent reply other threads:[~2012-03-06 10:09 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-03-02 21:32 [PATCH] dm thin: relax hard limit on the maximum size of a metadata device Mike Snitzer
2012-03-05 10:21 ` Joe Thornber
2012-03-05 14:04 ` Mike Snitzer
2012-03-05 14:19 ` Mike Snitzer
2012-03-06 10:09 ` Joe Thornber [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=20120306100952.GA5323@ubuntu \
--to=thornber@redhat.com \
--cc=dm-devel@redhat.com \
--cc=ejt@redhat.com \
--cc=snitzer@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.