RE: [PATCH 1/1] mm: Export a function to read vm_committed_as

[KY Srinivasan]

> -----Original Message-----
> From: David Rientjes [mailto:rientjes@xxxxxxxxxx]
> Sent: Monday, November 12, 2012 6:49 PM
> To: Dan Magenheimer
> Cc: KY Srinivasan; Konrad Wilk; gregkh@xxxxxxxxxxxxxxxxxxx; linux-
> kernel@xxxxxxxxxxxxxxx; devel@xxxxxxxxxxxxxxxxxxxxxx; olaf@xxxxxxxxx;
> apw@xxxxxxxxxxxxx; andi@xxxxxxxxxxxxxx; akpm@xxxxxxxxxxxxxxxxxxxx; linux-
> mm@xxxxxxxxx; kamezawa.hiroyuki@xxxxxxxxx; mhocko@xxxxxxx;
> hannes@xxxxxxxxxxx; yinghan@xxxxxxxxxx
> Subject: RE: [PATCH 1/1] mm: Export a function to read vm_committed_as
> 
> On Mon, 12 Nov 2012, Dan Magenheimer wrote:
> 
> > > > Why?  Is xen using it for a different inference?
> > >
> > > I think it is good to separate these patches. Dan (copied here) wrote the code
> for the
> > > Xen self balloon driver. If it is ok with him I can submit the patch for Xen as
> well.
> >
> > Hi KY --
> >
> > If I understand correctly, this would be only a cosmetic (function renaming)
> change
> > to the Xen selfballooning code.  If so, then I will be happy to Ack when I
> > see the patch.  However, Konrad (konrad.wilk@xxxxxxxxxx) is the maintainer
> > for all Xen code so you should ask him... and (from previous painful experience)
> > it can be difficult to sync even very simple interdependent changes going
> through
> > different maintainers without breaking linux-next.  So I can't offer any
> > help with that process, only commiseration. :-(
> >
> 
> I think this should be done in the same patch as the function getting
> introduced with a cc to Konrad and routed through -mm; even better,
> perhaps he'll have some useful comments for how this is used for xen that
> can be included for context.
> 
Ok; I will send out a single patch. I am hoping this can be applied soon as Hyper-V balloon
driver is queued behind this.

Regards,

K. Y



--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/