From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1756457AbYKEV3U (ORCPT ); Wed, 5 Nov 2008 16:29:20 -0500 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1753287AbYKEV3L (ORCPT ); Wed, 5 Nov 2008 16:29:11 -0500 Received: from nlpi025.sbcis.sbc.com ([207.115.36.54]:54720 "EHLO nlpi025.prodigy.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1753166AbYKEV3L (ORCPT ); Wed, 5 Nov 2008 16:29:11 -0500 Date: Wed, 5 Nov 2008 15:28:31 -0600 (CST) From: Christoph Lameter X-X-Sender: cl@quilx.com To: Andrew Morton cc: peterz@infradead.org, rientjes@google.com, npiggin@suse.de, menage@google.com, dfults@sgi.com, linux-kernel@vger.kernel.org, containers@lists.osdl.org, travis@sgi.com, steiner@sgi.com Subject: Re: [patch 0/7] cpuset writeback throttling In-Reply-To: <20081105125603.36d0c222.akpm@linux-foundation.org> Message-ID: References: <20081104124753.fb1dde5a.akpm@linux-foundation.org> <1225831988.7803.1939.camel@twins> <20081104131637.68fbe055.akpm@linux-foundation.org> <1225833710.7803.1993.camel@twins> <20081104135004.f1717fcf.akpm@linux-foundation.org> <20081104143534.b5c16147.akpm@linux-foundation.org> <20081104153610.bbfd5ed8.akpm@linux-foundation.org> <20081104190505.769b93ec.akpm@linux-foundation.org> <20081105104145.abd6fc91.akpm@linux-foundation.org> <20081105123150.d6628805.akpm@linux-foundation.org> <20081105125603.36d0c222.akpm@linux-foundation.org> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Spam-Score: -2.6 Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Wed, 5 Nov 2008, Andrew Morton wrote: > See, here's my problem: we have a pile of new code which fixes some > problem. But the problem seems to be fairly small - it only affects a > small number of sophisticated users and they already have workarounds > in place. Well yes... Great situation with those workarounds. > So the world wouldn't end if we just didn't merge it. Those users > stick with their workarounds and the kernel remains simpler and > smaller. > > How do we work out which is the best choice here? I don't have enough > information to do this. Not sure how to treat this. I am not involved with large NUMA at this point. So the people who are interested need to speak up if they want this.