Re: [rfc 0/2] Introducing VmFlags field into smaps output

From: Cyrill Gorcunov
Date: Mon Oct 22 2012 - 15:39:07 EST

On Mon, Oct 22, 2012 at 12:29:34PM -0700, Andrew Morton wrote:
> On Mon, 22 Oct 2012 23:14:52 +0400
> Cyrill Gorcunov <gorcunov@xxxxxxxxxx> wrote:
> > Hi guys, during c/r sessions we've found that there is no way at
> > the moment to fetch some VMA associated flags, such as mlock()
> > and madvise(), thus the patches in this series intorduce new field
> > into "smaps" output called VmFlags where all flags associated with
> > the particular VMA is shown in two letter mnemonic.
> >
> > Strictly speaking for c/r we only need mlock/madvise bits but it
> > has been said that providing just a few flags looks somehow inconsistent.
> > So all flags are here now.
> >
> > Please review. Comments and complains are quite welcome!
> Sigh, it's still a pretty nasty-looking interface. Better ideas are
> welcomed.

Well, one usable thing could be (I guess) to print only flags set. Since
usually not that many flags are set on vma. This would shrink output at

> I joined the patches into one, massaged the changelog a bit and added a
> couple more paragraphs explaining why we're doing this to ourselves.

To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at
Please read the FAQ at