linux-kernel - Re: [PATCH] - Improve drain pages performance on large systems

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:	Wed, 16 Feb 2011 09:00:59 +0900
From:	Minchan Kim <minchan.kim@...il.com>
To:	Jack Steiner <steiner@....com>
Cc:	linux-mm@...ck.org, akpm@...ux-foundation.org,
	linux-kernel@...r.kernel.org, Mel Gorman <mel@....ul.ie>,
	David Rientjes <rientjes@...gle.com>
Subject: Re: [PATCH] - Improve drain pages performance on large systems

On Wed, Feb 16, 2011 at 7:38 AM, Jack Steiner <steiner@....com> wrote:
>
> Heavy swapping within a cpuset causes frequent calls to drain_all_pages().
> This sends IPIs to all cpus to free PCP pages. In most cases, there are
> no pages to be freed on cpus outside of the swapping cpuset.
>
> Add checks to minimize locking and updates to potentially hot cachelines.
> Before acquiring locks, do a quick check to see if any pages are in the PCP
> queues. Exit if none.
>
> On a 128 node SGI UV system, this reduced the IPI overhead to cpus outside of the
> swapping cpuset by 38% and improved time to run a pass of the swaping test
> from 98 sec to 51 sec. These times are obviously test & configuration
> dependent but the improvements are significant.
>
>
> Signed-off-by: Jack Steiner <steiner@....com>
>
> ---
>  mm/page_alloc.c |   14 ++++++++++++++
>  1 file changed, 14 insertions(+)
>
> Index: linux/mm/page_alloc.c
> ===================================================================
> --- linux.orig/mm/page_alloc.c  2011-02-15 16:28:36.165921713 -0600
> +++ linux/mm/page_alloc.c       2011-02-15 16:29:43.085502487 -0600
> @@ -592,10 +592,24 @@ static void free_pcppages_bulk(struct zo
>        int batch_free = 0;
>        int to_free = count;
>
> +       /*
> +        * Quick scan of zones. If all are empty, there is nothing to do.
> +        */
> +       for (migratetype = 0; migratetype < MIGRATE_PCPTYPES; migratetype++) {
> +               struct list_head *list;
> +
> +               list = &pcp->lists[migratetype];
> +               if (!list_empty(list))
> +                       break;
> +       }
> +       if (migratetype == MIGRATE_PCPTYPES)
> +               return;
> +
>        spin_lock(&zone->lock);
>        zone->all_unreclaimable = 0;
>        zone->pages_scanned = 0;
>
> +       migratetype = 0;
>        while (to_free) {
>                struct page *page;
>                struct list_head *list;
>
> --
> To unsubscribe, send a message with 'unsubscribe linux-mm' in
> the body to majordomo@...ck.org.  For more info on Linux MM,
> see: http://www.linux-mm.org/ .
> Fight unfair telecom internet charges in Canada: sign http://stopthemeter.ca/
> Don't email: <a href=mailto:"dont@...ck.org"> email@...ck.org </a>
>

It does make sense to me.
Although new code looks to be rather costly in small box, anyway we
use the same logic  in while loop so cache would be hot. so cost would
be little.

But how about this? This one never affect fast-critical path.

diff --git a/mm/page_alloc.c b/mm/page_alloc.c
index ff7e158..2dfb61a 100644
--- a/mm/page_alloc.c
+++ b/mm/page_alloc.c
@@ -1095,8 +1095,10 @@ static void drain_pages(unsigned int cpu)
                pset = per_cpu_ptr(zone->pageset, cpu);

                pcp = &pset->pcp;
-               free_pcppages_bulk(zone, pcp->count, pcp);
-               pcp->count = 0;
+               if (pcp->count > 0) {
+                       free_pcppages_bulk(zone, pcp->count, pcp);
+                       pcp->count = 0;
+               }
                local_irq_restore(flags);
        }
 }



-- 
Kind regards,
Minchan Kim
--
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/