[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <20090820023740.GA12528@verge.net.au>
Date: Thu, 20 Aug 2009 12:37:41 +1000
From: Simon Horman <horms@...ge.net.au>
To: Ryo Tsuruta <ryov@...inux.co.jp>
Cc: agk@...hat.com, dm-devel@...hat.com, linux-kernel@...r.kernel.org,
containers@...ts.linux-foundation.org,
virtualization@...ts.linux-foundation.org,
xen-devel@...ts.xensource.com
Subject: Re: [PATCH] dm-ioband-v1.12.3: I/O bandwidth controller
On Fri, Aug 07, 2009 at 10:36:40AM +0900, Ryo Tsuruta wrote:
> Hi Alasdair,
>
> Ryo Tsuruta <ryov@...inux.co.jp> wrote:
> > Hi Alasdair,
> >
> > This is dm-ioband v1.12.3 release that is a minor update to avoid
> > sparse warnings other than related to the event tracing. (I used
> > sparse-2009-07-29.)
> >
> > This patch can be applied to the current dm-devel tree and 2.6.31-rc4,
> > so could you please replace dm-add-ioband.patch in your tree with this?
> > And I would appreciate it if you would let me know your thoughts about
> > merging dm-ioband to upstream.
>
> The dm-ioband patch in the dm-devel tree is still older. Could you
> please update it with the new patch? And could you please let me know
> your thoughts about dm-ioband?
Hi Alasdiar,
I'm wondering if you see any problems with merging dm-ioband at this time.
I'm eager to address any such concerns.
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists