Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1754845Ab3CKV1R (ORCPT ); Mon, 11 Mar 2013 17:27:17 -0400 Received: from mail-ie0-f171.google.com ([209.85.223.171]:57455 "EHLO mail-ie0-f171.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1754774Ab3CKVPW (ORCPT ); Mon, 11 Mar 2013 17:15:22 -0400 MIME-Version: 1.0 In-Reply-To: <20130311210628.GG14738@redhat.com> References: <513E28B8.3000502@zytor.com> <20130311192021.GF12107@redhat.com> <513E36CB.5040908@zytor.com> <20130311201245.GC14738@redhat.com> <513E3C44.9030402@zytor.com> <87hakhk6xu.fsf@xmission.com> <20130311204530.GE14738@redhat.com> <20130311210628.GG14738@redhat.com> Date: Mon, 11 Mar 2013 14:15:21 -0700 X-Google-Sender-Auth: xrWHOJC4Mycv1ol1NC-bOrFZDZs Message-ID: Subject: Re: [PATCH] x86, kdump: Set crashkernel_low automatically From: Yinghai Lu To: Vivek Goyal Cc: "Eric W. Biederman" , "H. Peter Anvin" , Konrad Rzeszutek Wilk , Thomas Gleixner , Ingo Molnar , WANG Chao , linux-kernel@vger.kernel.org Content-Type: text/plain; charset=ISO-8859-1 Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1993 Lines: 42 On Mon, Mar 11, 2013 at 2:06 PM, Vivek Goyal wrote: > On Mon, Mar 11, 2013 at 01:57:41PM -0700, Yinghai Lu wrote: >> On Mon, Mar 11, 2013 at 1:45 PM, Vivek Goyal wrote: >> > In my experience, trying to keep foot-print small has kind of been a >> > losing battle. >> > >> > - People want more functionality in second kernel, want to dump to more >> > complicated IO stacks and that requires pulling in more drivers, >> > more libraries, more daemons, more user space tools and what not. >> > >> > - Now we use dracut generated initramfs and it has been growing in size. >> > Now systemd has been pulled in too. >> > >> > - Drivers keep on increasing their memory usage. >> >> If the dump file will be only put one place, why should all the drivers >> for all devices get loaded? >> for example: dump will be on disk with one scsi controller, can you only >> load driver that contoller? and forget about all other storage controller and >> network etc drivers. > > We do try to optimize things this way. Only include drivers as needed. But > a single driver might be handling lots of cards and then try to bring > up all the cards in second kernel. Can you disable auto_probe at first? and then use /sys bind driver to specific device. > > Just fixed some issues with one driver where around 40MB extra memory > was benig consumed because of multiqueue support. Just bunch of allocation > in driver. And we used kernel command line to disable it. Yes that the is one problem, we should have some facility or helpers to reject those invalid request. and driver should reduce their foot print step by step. for example, we only have 64M, but first driver want to alloc 32M, it should be just rejected. -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/