From: rppt@linux.vnet.ibm.com (Mike Rapoport)
To: linux-arm-kernel@lists.infradead.org
Subject: KSM not working in 4.9 Kernel
Date: Mon, 17 Sep 2018 07:37:24 +0300 [thread overview]
Message-ID: <20180917043724.GA12866@rapoport-lnx> (raw)
In-Reply-To: <CAOuPNLj0HyC+yzwTpN-EWpzHTJ58u7pBfOja1MyweF4pbct1eQ@mail.gmail.com>
On Sun, Sep 16, 2018 at 10:35:17PM +0530, Pintu Kumar wrote:
> On Sun, Sep 16, 2018 at 9:02 PM Mike Rapoport <rppt@linux.vnet.ibm.com> wrote:
> >
> > On Fri, Sep 14, 2018 at 07:58:01PM +0530, Pintu Kumar wrote:
> > > Hi All,
> > >
> > > Board: Hikey620 ARM64
> > > Kernel: 4.9.20
> > >
> > > I am trying to verify KSM (Kernel Same Page Merging) functionality on
> > > 4.9 Kernel using "mmap" and madvise user space test utility.
> > > But to my observation, it seems KSM is not working for me.
> > > CONFIG_KSM=y is enabled in kernel.
> > > ksm_init is also called during boot up.
> > > 443 ? SN 0:00 [ksmd]
> > >
> > > ksmd thread is also running.
> > >
> > > However, when I see the sysfs, no values are written.
> > > ~ # grep -H '' /sys/kernel/mm/ksm/*
> > > /sys/kernel/mm/ksm/pages_hashed:0
> > > /sys/kernel/mm/ksm/pages_scanned:0
> > > /sys/kernel/mm/ksm/pages_shared:0
> > > /sys/kernel/mm/ksm/pages_sharing:0
> > > /sys/kernel/mm/ksm/pages_to_scan:200
> > > /sys/kernel/mm/ksm/pages_unshared:0
> > > /sys/kernel/mm/ksm/pages_volatile:0
> > > /sys/kernel/mm/ksm/run:1
> > > /sys/kernel/mm/ksm/sleep_millisecs:1000
> > >
> > > So, please let me know if I am doing any thing wrong.
> > >
> > > This is the test utility:
> > > int main(int argc, char *argv[])
> > > {
> > > int i, n, size;
> > > char *buffer;
> > > void *addr;
> > >
> > > n = 100;
> > > size = 100 * getpagesize();
> > > for (i = 0; i < n; i++) {
> > > buffer = (char *)malloc(size);
> > > memset(buffer, 0xff, size);
> > > addr = mmap(NULL, size,
> > > PROT_READ | PROT_EXEC | PROT_WRITE,
> > > MAP_PRIVATE | MAP_ANONYMOUS,
> > > -1, 0);
> > > madvise(addr, size, MADV_MERGEABLE);
> >
> > Just mmap'ing an area does not allocate any physical pages, so KSM has
> > nothing to merge.
> >
> > You need to memset(addr,...) after mmap().
> >
>
> Yes, I am doing memset also.
> memset(addr, 0xff, size);
>
> But still no effect.
> And I checked LTP test cases. It almost doing the same thing.
>
> I observed that [ksmd] thread is not waking up at all.
> I gave some print inside it, but I could never saw that prints coming.
> I could not find it running either in top command during the operation.
> Is there anything needs to be done, to wakw up ksmd?
> I already set: echo 1 > /sys/kernel/mm/ksm.
It should be echo 1 > /sys/kernel/mm/ksm/run
>
>
> > > sleep(1);
> > > }
> > > printf("Done....press ^C\n");
> > >
> > > pause();
> > >
> > > return 0;
> > > }
> > >
> > >
> > >
> > > Thanks,
> > > Pintu
> > >
> >
> > --
> > Sincerely yours,
> > Mike.
> >
>
--
Sincerely yours,
Mike.
WARNING: multiple messages have this Message-ID (diff)
From: Mike Rapoport <rppt@linux.vnet.ibm.com>
To: Pintu Kumar <pintu.ping@gmail.com>
Cc: open list <linux-kernel@vger.kernel.org>,
Russell King - ARM Linux <linux@armlinux.org.uk>,
linux-arm-kernel@lists.infradead.org, linux-mm@kvack.org
Subject: Re: KSM not working in 4.9 Kernel
Date: Mon, 17 Sep 2018 07:37:24 +0300 [thread overview]
Message-ID: <20180917043724.GA12866@rapoport-lnx> (raw)
In-Reply-To: <CAOuPNLj0HyC+yzwTpN-EWpzHTJ58u7pBfOja1MyweF4pbct1eQ@mail.gmail.com>
On Sun, Sep 16, 2018 at 10:35:17PM +0530, Pintu Kumar wrote:
> On Sun, Sep 16, 2018 at 9:02 PM Mike Rapoport <rppt@linux.vnet.ibm.com> wrote:
> >
> > On Fri, Sep 14, 2018 at 07:58:01PM +0530, Pintu Kumar wrote:
> > > Hi All,
> > >
> > > Board: Hikey620 ARM64
> > > Kernel: 4.9.20
> > >
> > > I am trying to verify KSM (Kernel Same Page Merging) functionality on
> > > 4.9 Kernel using "mmap" and madvise user space test utility.
> > > But to my observation, it seems KSM is not working for me.
> > > CONFIG_KSM=y is enabled in kernel.
> > > ksm_init is also called during boot up.
> > > 443 ? SN 0:00 [ksmd]
> > >
> > > ksmd thread is also running.
> > >
> > > However, when I see the sysfs, no values are written.
> > > ~ # grep -H '' /sys/kernel/mm/ksm/*
> > > /sys/kernel/mm/ksm/pages_hashed:0
> > > /sys/kernel/mm/ksm/pages_scanned:0
> > > /sys/kernel/mm/ksm/pages_shared:0
> > > /sys/kernel/mm/ksm/pages_sharing:0
> > > /sys/kernel/mm/ksm/pages_to_scan:200
> > > /sys/kernel/mm/ksm/pages_unshared:0
> > > /sys/kernel/mm/ksm/pages_volatile:0
> > > /sys/kernel/mm/ksm/run:1
> > > /sys/kernel/mm/ksm/sleep_millisecs:1000
> > >
> > > So, please let me know if I am doing any thing wrong.
> > >
> > > This is the test utility:
> > > int main(int argc, char *argv[])
> > > {
> > > int i, n, size;
> > > char *buffer;
> > > void *addr;
> > >
> > > n = 100;
> > > size = 100 * getpagesize();
> > > for (i = 0; i < n; i++) {
> > > buffer = (char *)malloc(size);
> > > memset(buffer, 0xff, size);
> > > addr = mmap(NULL, size,
> > > PROT_READ | PROT_EXEC | PROT_WRITE,
> > > MAP_PRIVATE | MAP_ANONYMOUS,
> > > -1, 0);
> > > madvise(addr, size, MADV_MERGEABLE);
> >
> > Just mmap'ing an area does not allocate any physical pages, so KSM has
> > nothing to merge.
> >
> > You need to memset(addr,...) after mmap().
> >
>
> Yes, I am doing memset also.
> memset(addr, 0xff, size);
>
> But still no effect.
> And I checked LTP test cases. It almost doing the same thing.
>
> I observed that [ksmd] thread is not waking up at all.
> I gave some print inside it, but I could never saw that prints coming.
> I could not find it running either in top command during the operation.
> Is there anything needs to be done, to wakw up ksmd?
> I already set: echo 1 > /sys/kernel/mm/ksm.
It should be echo 1 > /sys/kernel/mm/ksm/run
>
>
> > > sleep(1);
> > > }
> > > printf("Done....press ^C\n");
> > >
> > > pause();
> > >
> > > return 0;
> > > }
> > >
> > >
> > >
> > > Thanks,
> > > Pintu
> > >
> >
> > --
> > Sincerely yours,
> > Mike.
> >
>
--
Sincerely yours,
Mike.
next prev parent reply other threads:[~2018-09-17 4:37 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-09-14 14:28 KSM not working in 4.9 Kernel Pintu Kumar
2018-09-14 14:28 ` Pintu Kumar
2018-09-14 17:12 ` Yang Shi
2018-09-14 17:12 ` Yang Shi
2018-09-15 2:55 ` Pintu Kumar
2018-09-15 2:55 ` Pintu Kumar
2018-09-16 15:32 ` Mike Rapoport
2018-09-16 15:32 ` Mike Rapoport
2018-09-16 17:05 ` Pintu Kumar
2018-09-16 17:05 ` Pintu Kumar
2018-09-17 4:37 ` Mike Rapoport [this message]
2018-09-17 4:37 ` Mike Rapoport
2018-09-17 6:16 ` Pintu Kumar
2018-09-17 6:16 ` Pintu Kumar
2018-09-17 11:55 ` Pintu Kumar
2018-09-17 11:55 ` Pintu Kumar
2018-09-17 14:59 ` Mike Rapoport
2018-09-17 14:59 ` Mike Rapoport
2018-09-20 11:51 ` Pintu Kumar
2018-09-20 11:51 ` Pintu Kumar
2018-09-21 8:16 ` Mike Rapoport
2018-09-21 8:16 ` Mike Rapoport
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=20180917043724.GA12866@rapoport-lnx \
--to=rppt@linux.vnet.ibm.com \
--cc=linux-arm-kernel@lists.infradead.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.