xen-devel.lists.xenproject.org archive mirror
 help / color / mirror / Atom feed
From: "Jan Beulich" <JBeulich@novell.com>
To: Ky Srinivasan <KSrinivasan@novell.com>
Cc: Jeremy Fitzhardinge <jeremy@goop.org>, xen-devel@lists.xensource.com
Subject: Re: [PATCH]: Support dynamic resizing of vbds
Date: Mon, 22 Mar 2010 08:47:40 +0000	[thread overview]
Message-ID: <4BA73CBC0200007800036216@vpn.id2.novell.com> (raw)
In-Reply-To: <4BA244F50200003000081870@sinclair.provo.novell.com>

Based on the location of the file patched, it this would seem to be 
targeted at the 2.6.18 tree, but then 2.6.18 does not have a
revalidate_disk() function (introduced only in .28). What's the deal
here? Should this perhaps be carried out by open coding in blkfront
what .28 does?

Thanks, Jan

>>> "Ky Srinivasan" <ksrinivasan@novell.com> 18.03.10 22:21 >>>


>>> On 3/18/2010 at  5:01 PM, in message <4BA294A0.1010900@goop.org>, Jeremy
Fitzhardinge <jeremy@goop.org> wrote: 
> On 03/18/2010 01:28 PM, Ky Srinivasan wrote:
>> The attached patch supports dynamic resizing of vbds. This patch fixes a bug 
> in the previous version of this patch that was sent out. With this patch you 
> can perform "online" resizing of  file systems that support online resizing.
>>    
> 
> Please send a delta against the previous patch, since it has already 
> been applied.
I am attaching a new patch that is the delta on the previous one.

Signed-off-by: K. Y. Srinivasan <ksrinivasan@novell.com>




> 
>      J

  reply	other threads:[~2010-03-22  8:47 UTC|newest]

Thread overview: 47+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-03-18 20:28 [PATCH]: Support dynamic resizing of vbds Ky Srinivasan
2010-03-18 21:01 ` Jeremy Fitzhardinge
2010-03-18 21:21   ` Ky Srinivasan
2010-03-22  8:47     ` Jan Beulich [this message]
2010-03-22  9:15       ` J. Roeleveld
2010-03-22  9:23         ` Jan Beulich
2010-03-22  9:42           ` J. Roeleveld
2010-03-22 10:40             ` Pasi Kärkkäinen
2010-07-20 17:28   ` Pasi Kärkkäinen
2010-07-20 17:37     ` Jeremy Fitzhardinge
2010-07-20 18:29       ` Pasi Kärkkäinen
2010-07-20 19:49         ` Jeremy Fitzhardinge
2010-07-24 13:43           ` Pasi Kärkkäinen
2010-04-04  9:57 ` J. Roeleveld
2010-04-05 16:45   ` Ky Srinivasan
  -- strict thread matches above, loose matches on Subject: below --
2010-03-22 22:06 Ky Srinivasan
2010-03-23  7:17 ` Pasi Kärkkäinen
2010-03-09 19:56 Ky Srinivasan
2010-03-09 20:15 ` Pasi Kärkkäinen
2010-03-09 20:31   ` Ky Srinivasan
2010-03-09 20:35     ` Pasi Kärkkäinen
2010-03-09 20:39       ` Ky Srinivasan
2010-03-11 20:15         ` Pasi Kärkkäinen
2010-03-11 21:44           ` Jeremy Fitzhardinge
2010-03-11 22:01             ` Ky Srinivasan
2010-03-11 23:13               ` Jeremy Fitzhardinge
2010-03-12  2:52                 ` Ky Srinivasan
2010-03-12 10:41 ` J. Roeleveld
2010-03-14 13:49   ` Andrew Lyon
2010-03-14 14:06     ` Pasi Kärkkäinen
2010-03-16  3:04       ` Ky Srinivasan
2010-03-16  3:05       ` Ky Srinivasan
2010-07-20 18:27         ` Pasi Kärkkäinen
2010-07-20 18:43           ` Ky Srinivasan
2010-07-20 18:50             ` Pasi Kärkkäinen
2010-07-20 18:52               ` Ky Srinivasan
2010-07-20 19:00                 ` J. Roeleveld
2010-07-20 19:06                   ` Pasi Kärkkäinen
2010-07-28 18:59                     ` Ky Srinivasan
2010-03-16  2:50     ` Ky Srinivasan
2010-03-16 21:24       ` J. Roeleveld
2010-03-16 21:27         ` J. Roeleveld
2010-03-16 22:04           ` J. Roeleveld
2010-03-17 15:33           ` Ky Srinivasan
2010-03-17 15:09         ` Ky Srinivasan
2010-03-16  3:03     ` Ky Srinivasan
2010-03-15  9:26 ` Jan Beulich

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=4BA73CBC0200007800036216@vpn.id2.novell.com \
    --to=jbeulich@novell.com \
    --cc=KSrinivasan@novell.com \
    --cc=jeremy@goop.org \
    --cc=xen-devel@lists.xensource.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).