From: Mel Gorman <mgorman@suse.de> To: Greg KH <greg@kroah.com> Cc: Stable <stable@vger.kernel.org>, Linux-MM <linux-mm@kvack.org>, LKML <linux-kernel@vger.kernel.org> Subject: Re: [PATCH 00/34] Memory management performance backports for -stable V2 Date: Wed, 25 Jul 2012 23:48:52 +0100 [thread overview] Message-ID: <20120725224852.GF9222@suse.de> (raw) In-Reply-To: <20120725223057.GA4253@kroah.com> On Wed, Jul 25, 2012 at 03:30:57PM -0700, Greg KH wrote: > > <SNIP> > > All of the patches will apply to 3.0-stable but the ordering of the > > patches is such that applying them to 3.2-stable and 3.4-stable should > > be straight-forward. > > I can't find any of these that should have gone to 3.4-stable, given > that they all were included in 3.4 already, right? > Yes, you're right. At the time I wrote the changelog I had patches belonging to 3.5 included. I later decided to drop them until after 3.5 was out. It was potentially weird to have a 3.0-stable kernel with patches that were not in a released 3.x.0 kernel. Besides, they were very low priority. I forgot to update the changelog to match. > I've queued up the whole lot for the 3.0-stable tree, thanks so much for > providing them. > Thanks for reviewing them in detail and getting the flaws corrected. I expect it'll be a bit more smooth if/when I do something like this again. -- Mel Gorman SUSE Labs
WARNING: multiple messages have this Message-ID (diff)
From: Mel Gorman <mgorman@suse.de> To: Greg KH <greg@kroah.com> Cc: Stable <stable@vger.kernel.org>, Linux-MM <linux-mm@kvack.org>, LKML <linux-kernel@vger.kernel.org> Subject: Re: [PATCH 00/34] Memory management performance backports for -stable V2 Date: Wed, 25 Jul 2012 23:48:52 +0100 [thread overview] Message-ID: <20120725224852.GF9222@suse.de> (raw) In-Reply-To: <20120725223057.GA4253@kroah.com> On Wed, Jul 25, 2012 at 03:30:57PM -0700, Greg KH wrote: > > <SNIP> > > All of the patches will apply to 3.0-stable but the ordering of the > > patches is such that applying them to 3.2-stable and 3.4-stable should > > be straight-forward. > > I can't find any of these that should have gone to 3.4-stable, given > that they all were included in 3.4 already, right? > Yes, you're right. At the time I wrote the changelog I had patches belonging to 3.5 included. I later decided to drop them until after 3.5 was out. It was potentially weird to have a 3.0-stable kernel with patches that were not in a released 3.x.0 kernel. Besides, they were very low priority. I forgot to update the changelog to match. > I've queued up the whole lot for the 3.0-stable tree, thanks so much for > providing them. > Thanks for reviewing them in detail and getting the flaws corrected. I expect it'll be a bit more smooth if/when I do something like this again. -- Mel Gorman SUSE Labs -- 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>
next prev parent reply other threads:[~2012-07-25 22:48 UTC|newest] Thread overview: 117+ messages / expand[flat|nested] mbox.gz Atom feed top 2012-07-23 13:38 [PATCH 00/34] Memory management performance backports for -stable V2 Mel Gorman 2012-07-23 13:38 ` Mel Gorman 2012-07-23 13:38 ` [PATCH 01/34] mm: vmstat: cache align vm_stat Mel Gorman 2012-07-23 13:38 ` Mel Gorman 2012-07-23 13:38 ` [PATCH 02/34] mm: memory hotplug: Check if pages are correctly reserved on a per-section basis Mel Gorman 2012-07-23 13:38 ` Mel Gorman 2012-07-23 13:38 ` [PATCH 03/34] mm: Reduce the amount of work done when updating min_free_kbytes Mel Gorman 2012-07-23 13:38 ` Mel Gorman 2012-07-24 22:47 ` Greg KH 2012-07-24 22:47 ` Greg KH 2012-07-25 7:57 ` Mel Gorman 2012-07-25 7:57 ` Mel Gorman 2012-07-23 13:38 ` [PATCH 04/34] mm: vmscan: fix force-scanning small targets without swap Mel Gorman 2012-07-23 13:38 ` Mel Gorman 2012-07-23 13:38 ` [PATCH 05/34] vmscan: clear ZONE_CONGESTED for zone with good watermark Mel Gorman 2012-07-23 13:38 ` Mel Gorman 2012-07-23 13:38 ` [PATCH 06/34] vmscan: add shrink_slab tracepoints Mel Gorman 2012-07-23 13:38 ` Mel Gorman 2012-07-23 13:38 ` [PATCH 07/34] vmscan: shrinker->nr updates race and go wrong Mel Gorman 2012-07-23 13:38 ` Mel Gorman 2012-07-23 13:38 ` [PATCH 08/34] vmscan: reduce wind up shrinker->nr when shrinker can't do work Mel Gorman 2012-07-23 13:38 ` Mel Gorman 2012-07-23 13:38 ` [PATCH 09/34] mm: limit direct reclaim for higher order allocations Mel Gorman 2012-07-23 13:38 ` Mel Gorman 2012-07-23 13:38 ` [PATCH 10/34] mm: Abort reclaim/compaction if compaction can proceed Mel Gorman 2012-07-23 13:38 ` Mel Gorman 2012-07-23 13:38 ` [PATCH 11/34] mm: compaction: trivial clean up in acct_isolated() Mel Gorman 2012-07-23 13:38 ` Mel Gorman 2012-07-23 13:38 ` [PATCH 12/34] mm: change isolate mode from #define to bitwise type Mel Gorman 2012-07-23 13:38 ` Mel Gorman 2012-07-23 13:38 ` [PATCH 13/34] mm: compaction: make isolate_lru_page() filter-aware Mel Gorman 2012-07-23 13:38 ` Mel Gorman 2012-07-23 13:38 ` [PATCH 14/34] mm: zone_reclaim: " Mel Gorman 2012-07-23 13:38 ` Mel Gorman 2012-07-23 13:38 ` [PATCH 15/34] mm: migration: clean up unmap_and_move() Mel Gorman 2012-07-23 13:38 ` Mel Gorman 2012-07-25 15:45 ` Greg KH 2012-07-25 15:45 ` Greg KH 2012-07-25 16:04 ` Mel Gorman 2012-07-25 16:04 ` Mel Gorman 2012-07-25 18:03 ` Greg KH 2012-07-25 18:03 ` Greg KH 2012-07-23 13:38 ` [PATCH 16/34] mm: compaction: Allow compaction to isolate dirty pages Mel Gorman 2012-07-23 13:38 ` Mel Gorman 2012-07-25 15:47 ` Greg KH 2012-07-25 15:47 ` Greg KH 2012-07-25 16:07 ` Mel Gorman 2012-07-25 16:07 ` Mel Gorman 2012-07-23 13:38 ` [PATCH 17/34] mm: compaction: Determine if dirty pages can be migrated without blocking within ->migratepage Mel Gorman 2012-07-23 13:38 ` Mel Gorman 2012-07-23 13:38 ` [PATCH 18/34] mm: page allocator: Do not call direct reclaim for THP allocations while compaction is deferred Mel Gorman 2012-07-23 13:38 ` Mel Gorman 2012-07-23 13:38 ` [PATCH 19/34] mm: compaction: make isolate_lru_page() filter-aware again Mel Gorman 2012-07-23 13:38 ` Mel Gorman 2012-07-23 13:38 ` [PATCH 20/34] kswapd: avoid unnecessary rebalance after an unsuccessful balancing Mel Gorman 2012-07-23 13:38 ` Mel Gorman 2012-07-23 13:38 ` [PATCH 21/34] kswapd: assign new_order and new_classzone_idx after wakeup in sleeping Mel Gorman 2012-07-23 13:38 ` Mel Gorman 2012-07-23 13:38 ` [PATCH 22/34] mm: compaction: Introduce sync-light migration for use by compaction Mel Gorman 2012-07-23 13:38 ` Mel Gorman 2012-07-23 13:38 ` [PATCH 23/34] mm: vmscan: When reclaiming for compaction, ensure there are sufficient free pages available Mel Gorman 2012-07-23 13:38 ` Mel Gorman 2012-07-23 13:38 ` [PATCH 24/34] mm: vmscan: Do not OOM if aborting reclaim to start compaction Mel Gorman 2012-07-23 13:38 ` Mel Gorman 2012-07-23 13:38 ` [PATCH 25/34] mm: vmscan: Check if reclaim should really abort even if compaction_ready() is true for one zone Mel Gorman 2012-07-23 13:38 ` Mel Gorman 2012-07-25 19:51 ` Greg KH 2012-07-25 19:51 ` Greg KH 2012-07-23 13:38 ` [PATCH 26/34] vmscan: promote shared file mapped pages Mel Gorman 2012-07-23 13:38 ` Mel Gorman 2012-07-23 13:38 ` [PATCH 27/34] vmscan: activate executable pages after first usage Mel Gorman 2012-07-23 13:38 ` Mel Gorman 2012-07-23 13:38 ` [PATCH 28/34] mm/vmscan.c: consider swap space when deciding whether to continue reclaim Mel Gorman 2012-07-23 13:38 ` Mel Gorman 2012-07-23 13:38 ` [PATCH 29/34] mm: test PageSwapBacked in lumpy reclaim Mel Gorman 2012-07-23 13:38 ` Mel Gorman 2012-07-23 13:38 ` [PATCH 30/34] mm: vmscan: Do not force kswapd to scan small targets Mel Gorman 2012-07-23 13:38 ` Mel Gorman 2012-07-25 19:59 ` Greg KH 2012-07-25 19:59 ` Greg KH 2012-07-25 21:35 ` Mel Gorman 2012-07-25 21:35 ` Mel Gorman 2012-07-25 21:44 ` Greg KH 2012-07-25 21:44 ` Greg KH 2012-07-23 13:38 ` [PATCH 31/34] cpusets: avoid looping when storing to mems_allowed if one node remains set Mel Gorman 2012-07-23 13:38 ` Mel Gorman 2012-07-23 13:38 ` [PATCH 32/34] cpusets: stall when updating mems_allowed for mempolicy or disjoint nodemask Mel Gorman 2012-07-23 13:38 ` Mel Gorman 2012-07-23 13:38 ` [PATCH 33/34] cpuset: mm: Reduce large amounts of memory barrier related damage v3 Mel Gorman 2012-07-23 13:38 ` Mel Gorman 2012-07-23 13:38 ` [PATCH 34/34] mm/hugetlb: fix warning in alloc_huge_page/dequeue_huge_page_vma Mel Gorman 2012-07-23 13:38 ` Mel Gorman 2012-07-24 5:58 ` [PATCH 00/34] Memory management performance backports for -stable V2 Mike Galbraith 2012-07-24 5:58 ` Mike Galbraith 2012-07-24 8:10 ` Mel Gorman 2012-07-24 8:10 ` Mel Gorman 2012-07-24 13:18 ` Hillf Danton 2012-07-24 13:18 ` Hillf Danton 2012-07-24 13:27 ` Mel Gorman 2012-07-24 13:27 ` Mel Gorman 2012-07-24 13:34 ` Hillf Danton 2012-07-24 13:34 ` Hillf Danton 2012-07-24 13:53 ` Mel Gorman 2012-07-24 13:53 ` Mel Gorman 2012-07-24 14:11 ` Hillf Danton 2012-07-24 14:11 ` Hillf Danton 2012-07-24 13:52 ` Mike Galbraith 2012-07-24 13:52 ` Mike Galbraith 2012-07-24 14:18 ` Hillf Danton 2012-07-24 14:18 ` Hillf Danton 2012-07-24 14:41 ` Mike Galbraith 2012-07-24 14:41 ` Mike Galbraith 2012-07-25 22:30 ` Greg KH 2012-07-25 22:30 ` Greg KH 2012-07-25 22:48 ` Mel Gorman [this message] 2012-07-25 22:48 ` Mel Gorman 2012-07-30 1:13 ` Ben Hutchings
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=20120725224852.GF9222@suse.de \ --to=mgorman@suse.de \ --cc=greg@kroah.com \ --cc=linux-kernel@vger.kernel.org \ --cc=linux-mm@kvack.org \ --cc=stable@vger.kernel.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: linkBe 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.