mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Marek Szyprowski <m.szyprowski@samsung.com>
To: "'Stephen Rothwell'" <sfr@canb.auug.org.au>,
	"'Andrew Morton'" <akpm@linux-foundation.org>
Cc: linux-next@vger.kernel.org, linux-kernel@vger.kernel.org,
	"'Kyungmin Park'" <kyungmin.park@samsung.com>
Subject: RE: linux-next: manual merge of the akpm tree with the dma-mapping tree
Date: Mon, 23 Apr 2012 09:50:53 +0200	[thread overview]
Message-ID: <056601cd2125$cf4737b0$6dd5a710$%szyprowski@samsung.com> (raw)
In-Reply-To: <20120423164953.1095c9ccbf81a33641947cd3@canb.auug.org.au>

Hi Stephen,

On Monday, April 23, 2012 8:50 AM Stephen Rothwell wrote:

> Today's linux-next merge of the scsi-post-merge tree got a conflict in
> mm/page_alloc.c between commit ac77c4123661 ("mm: trigger page reclaim in
> alloc_contig_range() to stabilise watermarks") from the dma-mapping tree
> and commit "mm: add extra free kbytes tunable" from the akpm tree.
> 
> Just context changes.  I fixed it up (I think - see below) and can carry
> the fixes as necessary.
> --
> Cheers,
> Stephen Rothwell                    sfr@canb.auug.org.au
> 
> diff --cc mm/page_alloc.c
> index 0e1c6f5,decfbf0..0000000
> --- a/mm/page_alloc.c
> +++ b/mm/page_alloc.c
> @@@ -5032,9 -4988,17 +5044,10 @@@ static void setup_per_zone_lowmem_reser
>   	calculate_totalreserve_pages();
>   }
> 
>  -/**
>  - * setup_per_zone_wmarks - called when min_free_kbytes changes
>  - * or when memory is hot-{added|removed}
>  - *
>  - * Ensures that the watermark[min,low,high] values for each zone are set
>  - * correctly with respect to min_free_kbytes.
>  - */
>  -void setup_per_zone_wmarks(void)
>  +static void __setup_per_zone_wmarks(void)
>   {
>   	unsigned long pages_min = min_free_kbytes >> (PAGE_SHIFT - 10);
> + 	unsigned long pages_low = extra_free_kbytes >> (PAGE_SHIFT - 10);
>   	unsigned long lowmem_pages = 0;
>   	struct zone *zone;
>   	unsigned long flags;
> @@@ -5074,16 -5041,13 +5090,18 @@@
>   			 * If it's a lowmem zone, reserve a number of pages
>   			 * proportionate to the zone's size.
>   			 */
> - 			zone->watermark[WMARK_MIN] = tmp;
> + 			zone->watermark[WMARK_MIN] = min;
>   		}
> 
> - 		zone->watermark[WMARK_LOW]  = min_wmark_pages(zone) + (tmp >> 2);
> - 		zone->watermark[WMARK_HIGH] = min_wmark_pages(zone) + (tmp >> 1);
> + 		zone->watermark[WMARK_LOW]  = min_wmark_pages(zone) +
> + 					low + (min >> 2);
> + 		zone->watermark[WMARK_HIGH] = min_wmark_pages(zone) +
> + 					low + (min >> 1);
>  +
>  +		zone->watermark[WMARK_MIN] += cma_wmark_pages(zone);
>  +		zone->watermark[WMARK_LOW] += cma_wmark_pages(zone);
>  +		zone->watermark[WMARK_HIGH] += cma_wmark_pages(zone);
>  +
>   		setup_zone_migrate_reserve(zone);
>   		spin_unlock_irqrestore(&zone->lock, flags);
>   	}

The fix looks fine, thanks for merging those patches.

Best regards
-- 
Marek Szyprowski
Samsung Poland R&D Center




  reply	other threads:[~2012-04-23  7:51 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-04-23  6:49 Stephen Rothwell
2012-04-23  7:50 ` Marek Szyprowski [this message]
2018-10-02  8:31 Stephen Rothwell

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='056601cd2125$cf4737b0$6dd5a710$%szyprowski@samsung.com' \
    --to=m.szyprowski@samsung.com \
    --cc=akpm@linux-foundation.org \
    --cc=kyungmin.park@samsung.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-next@vger.kernel.org \
    --cc=sfr@canb.auug.org.au \
    /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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

all inboxes | Powered by JetHome®