All of lore.kernel.org
 help / color / mirror / Atom feed
From: Rik van Riel <riel@redhat.com>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: linux-mm@kvack.org, aarcange@redhat.com, peterz@infradead.org,
	minchan@gmail.com, kosaki.motohiro@gmail.com,
	andi@firstfloor.org, hannes@cmpxchg.org, mel@csn.ul.ie,
	linux-kernel@vger.kernel.org, Rik van Riel <riel@surriel.com>
Subject: Re: [PATCH -mm 4/7] mm: make page colouring code generic
Date: Thu, 21 Jun 2012 13:52:14 -0400	[thread overview]
Message-ID: <4FE35F4E.3080002@redhat.com> (raw)
In-Reply-To: <20120619162747.fa31c86a.akpm@linux-foundation.org>

On 06/19/2012 07:27 PM, Andrew Morton wrote:
> On Mon, 18 Jun 2012 18:05:23 -0400
> Rik van Riel<riel@redhat.com>  wrote:
>
>> From: Rik van Riel<riel@surriel.com>
>>
>> Fix the x86-64 page colouring code to take pgoff into account.
>
> Could we please have a full description of what's wrong with the
> current code?

Here is a copy of the text I added to the changelog:


The old x86 code will always align the mmap
to aliasing boundaries, even if the program mmaps
the file with a non-zero pgoff.

If program A mmaps the file with pgoff 0, and
program B mmaps the file with pgoff 1. The old
code would align the mmaps, resulting in misaligned
pages:

A:  0123
B:  123

After this patch, they are aligned so the pages
line up:

A: 0123
B:  123

>> Use the x86 and MIPS page colouring code as the basis for a generic
>> page colouring function.

Renamed to "cache alignment", by Andi's request.

>> Teach the generic arch_get_unmapped_area(_topdown) code to call the
>> page colouring code.
>>
>> Make sure that ALIGN_DOWN always aligns down, and ends up at the
>> right page colour.
>
> Some performance tests on the result would be interesting.  iirc, we've
> often had trouble demonstrating much or any benefit from coloring.

On AMD Bulldozer, I do not know what the benefits are.

On ARM, MIPS, SPARC and SH, the main benefit is avoiding
data corruption :)

These architectures have VIPT caches on some CPU models,
and MAP_SHARED read-write mappings have to be properly
aligned to guarantee data consistency.

--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org.  For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>

WARNING: multiple messages have this Message-ID (diff)
From: Rik van Riel <riel@redhat.com>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: linux-mm@kvack.org, aarcange@redhat.com, peterz@infradead.org,
	minchan@gmail.com, kosaki.motohiro@gmail.com,
	andi@firstfloor.org, hannes@cmpxchg.org, mel@csn.ul.ie,
	linux-kernel@vger.kernel.org, Rik van Riel <riel@surriel.com>
Subject: Re: [PATCH -mm 4/7] mm: make page colouring code generic
Date: Thu, 21 Jun 2012 13:52:14 -0400	[thread overview]
Message-ID: <4FE35F4E.3080002@redhat.com> (raw)
In-Reply-To: <20120619162747.fa31c86a.akpm@linux-foundation.org>

On 06/19/2012 07:27 PM, Andrew Morton wrote:
> On Mon, 18 Jun 2012 18:05:23 -0400
> Rik van Riel<riel@redhat.com>  wrote:
>
>> From: Rik van Riel<riel@surriel.com>
>>
>> Fix the x86-64 page colouring code to take pgoff into account.
>
> Could we please have a full description of what's wrong with the
> current code?

Here is a copy of the text I added to the changelog:


The old x86 code will always align the mmap
to aliasing boundaries, even if the program mmaps
the file with a non-zero pgoff.

If program A mmaps the file with pgoff 0, and
program B mmaps the file with pgoff 1. The old
code would align the mmaps, resulting in misaligned
pages:

A:  0123
B:  123

After this patch, they are aligned so the pages
line up:

A: 0123
B:  123

>> Use the x86 and MIPS page colouring code as the basis for a generic
>> page colouring function.

Renamed to "cache alignment", by Andi's request.

>> Teach the generic arch_get_unmapped_area(_topdown) code to call the
>> page colouring code.
>>
>> Make sure that ALIGN_DOWN always aligns down, and ends up at the
>> right page colour.
>
> Some performance tests on the result would be interesting.  iirc, we've
> often had trouble demonstrating much or any benefit from coloring.

On AMD Bulldozer, I do not know what the benefits are.

On ARM, MIPS, SPARC and SH, the main benefit is avoiding
data corruption :)

These architectures have VIPT caches on some CPU models,
and MAP_SHARED read-write mappings have to be properly
aligned to guarantee data consistency.


  reply	other threads:[~2012-06-21 19:06 UTC|newest]

Thread overview: 58+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-06-18 22:05 [PATCH -mm 0/7] mm: scalable and unified arch_get_unmapped_area Rik van Riel
2012-06-18 22:05 ` Rik van Riel
2012-06-18 22:05 ` [PATCH -mm 1/7] mm: track free size between VMAs in VMA rbtree Rik van Riel
2012-06-18 22:05   ` Rik van Riel
2012-06-19 23:25   ` Andrew Morton
2012-06-19 23:25     ` Andrew Morton
2012-06-21 11:01   ` Peter Zijlstra
2012-06-21 11:01     ` Peter Zijlstra
2012-06-21 11:07   ` Peter Zijlstra
2012-06-21 11:07     ` Peter Zijlstra
2012-06-21 14:47   ` Mel Gorman
2012-06-21 14:47     ` Mel Gorman
2012-06-18 22:05 ` [PATCH -mm 2/7] mm: get unmapped area from VMA tree Rik van Riel
2012-06-18 22:05   ` Rik van Riel
2012-06-21  9:01   ` Johannes Weiner
2012-06-21  9:01     ` Johannes Weiner
2012-06-21 13:17     ` Rik van Riel
2012-06-21 13:17       ` Rik van Riel
2012-06-21 16:50     ` Rik van Riel
2012-06-21 16:50       ` Rik van Riel
2012-06-21 16:16   ` Mel Gorman
2012-06-21 16:16     ` Mel Gorman
2012-06-21 17:27     ` Rik van Riel
2012-06-21 17:27       ` Rik van Riel
2012-06-21 21:06   ` Peter Zijlstra
2012-06-21 21:06     ` Peter Zijlstra
2012-06-18 22:05 ` [PATCH -mm 3/7] Allow each architecture to specify the address range that can be used for this allocation Rik van Riel
2012-06-18 22:05   ` Rik van Riel
2012-06-18 22:05 ` [PATCH -mm 4/7] mm: make page colouring code generic Rik van Riel
2012-06-18 22:05   ` Rik van Riel
2012-06-19 23:27   ` Andrew Morton
2012-06-19 23:27     ` Andrew Morton
2012-06-21 17:52     ` Rik van Riel [this message]
2012-06-21 17:52       ` Rik van Riel
2012-06-21 19:22       ` Borislav Petkov
2012-06-21 19:22         ` Borislav Petkov
2012-06-21 11:20   ` Peter Zijlstra
2012-06-21 11:20     ` Peter Zijlstra
2012-06-21 14:30     ` Rik van Riel
2012-06-21 14:30       ` Rik van Riel
2012-06-21 17:40       ` Andrew Morton
2012-06-21 17:40         ` Andrew Morton
2012-06-21 17:45         ` Rik van Riel
2012-06-21 17:45           ` Rik van Riel
2012-06-21 12:37   ` Borislav Petkov
2012-06-21 12:37     ` Borislav Petkov
2012-06-21 13:24     ` Rik van Riel
2012-06-21 13:24       ` Rik van Riel
2012-06-18 22:05 ` [PATCH -mm 5/7] mm: remove x86 arch_get_unmapped_area(_topdown) Rik van Riel
2012-06-18 22:05   ` Rik van Riel
2012-06-18 22:05 ` [PATCH -mm 6/7] remove MIPS arch_get_unmapped_area code Rik van Riel
2012-06-18 22:05   ` Rik van Riel
2012-06-18 22:05 ` [PATCH -mm 7/7] remove ARM arch_get_unmapped_area functions Rik van Riel
2012-06-18 22:05   ` Rik van Riel
2012-06-19 23:20 ` [PATCH -mm 0/7] mm: scalable and unified arch_get_unmapped_area Andrew Morton
2012-06-19 23:20   ` Andrew Morton
2012-06-21 10:18 ` Johannes Weiner
2012-06-21 10:18   ` Johannes Weiner

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=4FE35F4E.3080002@redhat.com \
    --to=riel@redhat.com \
    --cc=aarcange@redhat.com \
    --cc=akpm@linux-foundation.org \
    --cc=andi@firstfloor.org \
    --cc=hannes@cmpxchg.org \
    --cc=kosaki.motohiro@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=mel@csn.ul.ie \
    --cc=minchan@gmail.com \
    --cc=peterz@infradead.org \
    --cc=riel@surriel.com \
    /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.