All of lore.kernel.org
 help / color / mirror / Atom feed
From: Andrew Morton <akpm@linux-foundation.org>
To: Mel Gorman <mel@csn.ul.ie>
Cc: mingo@elte.hu, stable@kernel.org, linux-mm@kvack.org,
	linux-kernel@vger.kernel.org, hugh.dickins@tiscali.co.uk,
	Lee.Schermerhorn@hp.com, kosaki.motohiro@jp.fujitsu.com,
	starlight@binnacle.cx, ebmunson@us.ibm.com, agl@us.ibm.com,
	apw@canonical.com, wli@movementarian.org
Subject: Re: [PATCH 0/2] Fixes for hugetlbfs-related problems on shared memory
Date: Wed, 27 May 2009 13:14:37 -0700	[thread overview]
Message-ID: <20090527131437.5870e342.akpm@linux-foundation.org> (raw)
In-Reply-To: <1243422749-6256-1-git-send-email-mel@csn.ul.ie>

On Wed, 27 May 2009 12:12:27 +0100
Mel Gorman <mel@csn.ul.ie> wrote:

> The following two patches are required to fix problems reported by
> starlight@binnacle.cx. The tests cases both involve two processes interacting
> with shared memory segments backed by hugetlbfs.

Thanks.

Both of these address http://bugzilla.kernel.org/show_bug.cgi?id=13302, yes?
I added that info to the changelogs, to close the loop.

Ingo, I'd propose merging both these together rather than routing one
via the x86 tree, OK?

Question is: when?  Are we confident enough to merge it into 2.6.30
now, or should we hold off for 2.6.30.1?  I guess we have a week or
more, and if the changes do break something, we can fix that in
2.6.30.1 ;)



WARNING: multiple messages have this Message-ID (diff)
From: Andrew Morton <akpm@linux-foundation.org>
To: Mel Gorman <mel@csn.ul.ie>
Cc: mingo@elte.hu, stable@kernel.org, linux-mm@kvack.org,
	linux-kernel@vger.kernel.org, hugh.dickins@tiscali.co.uk,
	Lee.Schermerhorn@hp.com, kosaki.motohiro@jp.fujitsu.com,
	starlight@binnacle.cx, ebmunson@us.ibm.com, agl@us.ibm.com,
	apw@canonical.com, wli@movementarian.org
Subject: Re: [PATCH 0/2] Fixes for hugetlbfs-related problems on shared memory
Date: Wed, 27 May 2009 13:14:37 -0700	[thread overview]
Message-ID: <20090527131437.5870e342.akpm@linux-foundation.org> (raw)
In-Reply-To: <1243422749-6256-1-git-send-email-mel@csn.ul.ie>

On Wed, 27 May 2009 12:12:27 +0100
Mel Gorman <mel@csn.ul.ie> wrote:

> The following two patches are required to fix problems reported by
> starlight@binnacle.cx. The tests cases both involve two processes interacting
> with shared memory segments backed by hugetlbfs.

Thanks.

Both of these address http://bugzilla.kernel.org/show_bug.cgi?id=13302, yes?
I added that info to the changelogs, to close the loop.

Ingo, I'd propose merging both these together rather than routing one
via the x86 tree, OK?

Question is: when?  Are we confident enough to merge it into 2.6.30
now, or should we hold off for 2.6.30.1?  I guess we have a week or
more, and if the changes do break something, we can fix that in
2.6.30.1 ;)


--
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>

  parent reply	other threads:[~2009-05-27 20:19 UTC|newest]

Thread overview: 38+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-05-27 11:12 [PATCH 0/2] Fixes for hugetlbfs-related problems on shared memory Mel Gorman
2009-05-27 11:12 ` Mel Gorman
2009-05-27 11:12 ` [PATCH 1/2] x86: Ignore VM_LOCKED when determining if hugetlb-backed page tables can be shared or not Mel Gorman
2009-05-27 11:12   ` Mel Gorman
2009-05-27 16:38   ` Eric B Munson
2009-05-27 23:18   ` Ingo Molnar
2009-05-27 23:18     ` Ingo Molnar
2009-05-28  8:55     ` Mel Gorman
2009-05-28  8:55       ` Mel Gorman
2009-05-27 11:12 ` [PATCH 2/2] mm: Account for MAP_SHARED mappings using VM_MAYSHARE and not VM_SHARED in hugetlbfs Mel Gorman
2009-05-27 11:12   ` Mel Gorman
2009-05-27 16:40   ` Eric B Munson
2009-05-27 20:14 ` Andrew Morton [this message]
2009-05-27 20:14   ` [PATCH 0/2] Fixes for hugetlbfs-related problems on shared memory Andrew Morton
2009-05-27 23:19   ` Ingo Molnar
2009-05-27 23:19     ` Ingo Molnar
2009-06-16  0:19     ` QUESTION: can netdev_alloc_skb() errors be reduced by tuning? starlight
2009-06-16  0:19       ` starlight
2009-06-16  2:26       ` Eric Dumazet
2009-06-16  2:26         ` Eric Dumazet
2009-06-16  4:12         ` starlight
2009-06-16  4:12           ` starlight
2009-06-16  6:12           ` Eric Dumazet
2009-06-16  6:12             ` Eric Dumazet
2009-06-16  6:12             ` Eric Dumazet
2009-07-05  3:44             ` Herbert Xu
2009-07-05  3:44               ` Herbert Xu
2009-07-05  3:44               ` Herbert Xu
2009-06-16  9:19       ` Mel Gorman
2009-06-16  9:19         ` Mel Gorman
2009-06-16 15:25         ` starlight
2009-06-16 15:25           ` starlight
2009-05-28  8:56   ` [PATCH 0/2] Fixes for hugetlbfs-related problems on shared memory Mel Gorman
2009-05-28  8:56     ` Mel Gorman
2009-06-08  1:25 ` starlight
2009-06-08  1:25   ` starlight
2009-06-08 10:24   ` Mel Gorman
2009-06-08 10:24     ` Mel Gorman

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=20090527131437.5870e342.akpm@linux-foundation.org \
    --to=akpm@linux-foundation.org \
    --cc=Lee.Schermerhorn@hp.com \
    --cc=agl@us.ibm.com \
    --cc=apw@canonical.com \
    --cc=ebmunson@us.ibm.com \
    --cc=hugh.dickins@tiscali.co.uk \
    --cc=kosaki.motohiro@jp.fujitsu.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=mel@csn.ul.ie \
    --cc=mingo@elte.hu \
    --cc=stable@kernel.org \
    --cc=starlight@binnacle.cx \
    --cc=wli@movementarian.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.