linux-kernel - Re: [RFC] move free page back to MIGRATE

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] [day] [month] [year] [list]

Date:	Mon, 17 Dec 2007 10:44:53 +0000
From:	Mel Gorman <mel@....ul.ie>
To:	Shaohua Li <shaohua.li@...el.com>
Cc:	lkml <linux-kernel@...r.kernel.org>,
	Andrew Morton <akpm@...ux-foundation.org>
Subject: Re: [RFC] move free page back to MIGRATE_MOVABLE?

On (13/12/07 13:19), Shaohua Li didst pronounce:
> pages are MIGRATE_MOVABLE initially, and fallback to other types. If the
> pages are freed, I wonder why not move them back to MIGRATE_MOVABLE.

Because there is no need, if a MIGRATE_MOVABLE allocation needs more pages,
they will be acquired during fallback which always steals the largest
block. Lets say that a MIGRATE_UNMOVABLE block is freed and it is larger
than pageblock_order. The next MIGRATE_MOVABLE allocation will find it during
fallback if necessary.

> This, for example, can help memory remove.
> 

I don't see how. When hot-removing, MIGRATE_MOVABLE blocks are considered
possible to remove but they are also considered movable if the pages are free.

> Thanks,
> Shaohua 
> 
> Index: linux/mm/page_alloc.c
> ===================================================================
> --- linux.orig/mm/page_alloc.c	2007-12-13 11:44:36.000000000 +0800
> +++ linux/mm/page_alloc.c	2007-12-13 12:04:59.000000000 +0800
> @@ -386,6 +386,9 @@ static inline int page_is_buddy(struct p
>  	return 0;
>  }
>  
> +int move_freepages(struct zone *zone,
> +			struct page *start_page, struct page *end_page,
> +			int migratetype);
>  /*
>   * Freeing function for a buddy system allocator.
>   *
> @@ -446,6 +449,17 @@ static inline void __free_one_page(struc
>  	list_add(&page->lru,
>  		&zone->free_area[order].free_list[migratetype]);
>  	zone->free_area[order].nr_free++;
> +
> +	if (order >= pageblock_order && migratetype != MIGRATE_MOVABLE) {
> +		struct page *tmp = page;
> +
> +		move_freepages(zone, page, page + (1 << order) - 1, MIGRATE_MOVABLE);
> +

This is unnecessary and affects a commonly used path. If a MOVABLE allocation
needs more pages later, it will find the large free block during fallback.

> +		while (tmp < page + (1 << order)) {
> +			set_pageblock_migratetype(tmp, MIGRATE_MOVABLE);
> +			tmp += pageblock_nr_pages;
> +		}
> +	}
>  }
>  
>  static inline int free_pages_check(struct page *page)
> 

-- 
Mel Gorman
Part-time Phd Student                          Linux Technology Center
University of Limerick                         IBM Dublin Software Lab
--
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/