From: Vivek Goyal <vgoyal@redhat.com>
To: Phillip Susi <psusi@ubuntu.com>
Cc: linux-kernel@vger.kernel.org, axboe@kernel.dk,
dm-devel@redhat.com, Karel Zak <kzak@redhat.com>,
maxim.patlasov@gmail.com
Subject: Re: [PATCH 0/2] block: online resize of disk partitions
Date: Mon, 13 Feb 2012 16:56:50 -0500 [thread overview]
Message-ID: <20120213215650.GE3130@redhat.com> (raw)
In-Reply-To: <20120213215039.GD3130@redhat.com>
On Mon, Feb 13, 2012 at 04:50:39PM -0500, Vivek Goyal wrote:
[..]
> > as well as to allow for the
> > possibility of extending the interface in the future to allow changing
> > the start as well as the length.
>
> Even if we allow changing start at some point of time, then IOCTL can
> remain the same and just the implementation will change in a backward
> compatible manner. Old tools still will continue to work as they have
> always been, and new ones can start passing "start" too.
Let me thake that back. Changes will not be backward compatible as
if old tools run on new kernel specifying start as 0, then change
will fail on newer kernels which might allow changing start too.
Do you really expect that changing start will really be useful? If yes,
then it does make a case for not leaving "start" undefined.
Thanks
Vivek
next prev parent reply other threads:[~2012-02-13 21:56 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-02-13 19:30 [PATCH 0/2] block: online resize of disk partitions Vivek Goyal
2012-02-13 19:30 ` [PATCH 1/2] block: add partition resize function to blkpg ioctl Vivek Goyal
2012-02-13 19:30 ` [PATCH 2/2] resizepart: Utility to resize a partition Vivek Goyal
2012-02-13 21:34 ` [PATCH 0/2] block: online resize of disk partitions Phillip Susi
2012-02-13 21:50 ` Vivek Goyal
2012-02-13 21:56 ` Vivek Goyal [this message]
2012-02-13 22:18 ` Phillip Susi
2012-02-13 22:24 ` Vivek Goyal
2012-02-14 1:24 ` Phillip Susi
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=20120213215650.GE3130@redhat.com \
--to=vgoyal@redhat.com \
--cc=axboe@kernel.dk \
--cc=dm-devel@redhat.com \
--cc=kzak@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=maxim.patlasov@gmail.com \
--cc=psusi@ubuntu.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).