From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1754255Ab2GXN1q (ORCPT ); Tue, 24 Jul 2012 09:27:46 -0400 Received: from cantor2.suse.de ([195.135.220.15]:42793 "EHLO mx2.suse.de" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751962Ab2GXN1p (ORCPT ); Tue, 24 Jul 2012 09:27:45 -0400 Date: Tue, 24 Jul 2012 14:27:41 +0100 From: Mel Gorman To: Hillf Danton Cc: Mike Galbraith , Stable , Linux-MM , LKML Subject: Re: [PATCH 00/34] Memory management performance backports for -stable V2 Message-ID: <20120724132741.GS9222@suse.de> References: <1343050727-3045-1-git-send-email-mgorman@suse.de> <1343109531.7412.47.camel@marge.simpson.net> MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-15 Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.21 (2010-09-15) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Tue, Jul 24, 2012 at 09:18:16PM +0800, Hillf Danton wrote: > On Tue, Jul 24, 2012 at 1:58 PM, Mike Galbraith wrote: > > FWIW, I'm all for performance backports. They do have a downside though > > (other than the risk of bugs slipping in, or triggering latent bugs). > > > > When the next enterprise kernel is built, marketeers ask for numbers to > > make potential customers drool over, and you _can't produce any_ because > > you wedged all the spiffy performance stuff into the crusty old kernel. > > > Well do your job please. > I would suggest the user in question use the normal support channels for resolving a potentially SLES-specific bug. -- Mel Gorman SUSE Labs