From mboxrd@z Thu Jan 1 00:00:00 1970 From: "Luis R. Rodriguez" Subject: Re: [RFC v2 3/6] kthread: warn on kill signal if not OOM Date: Thu, 11 Sep 2014 13:42:20 -0700 Message-ID: References: <20140905174925.GA12991@mtj.dyndns.org> <20140909224143.GB3154@mtj.dyndns.org> <1410302783.13298.50.camel@jarvis.lan> <5762134.BLS0EbmNJd@dtor-glaptop> <1410465565.10549.19.camel@jarvis> <20140911202354.GA2598@core.coreip.homeip.net> Mime-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Cc: James Bottomley , Tejun Heo , Lennart Poettering , Kay Sievers , Greg Kroah-Hartman , Wu Zhangjin , Takashi Iwai , Arjan van de Ven , "linux-kernel@vger.kernel.org" , Oleg Nesterov , hare@suse.com, Andrew Morton , Tetsuo Handa , Joseph Salisbury , Benjamin Poirier , Santosh Rastapur , One Thousand Gnomes , Tim Gardner , Pierre Fersing , Nagalakshmi Nandigama , Praveen Krishnamoorthy Return-path: In-Reply-To: <20140911202354.GA2598@core.coreip.homeip.net> Sender: linux-scsi-owner@vger.kernel.org List-Id: netdev.vger.kernel.org On Thu, Sep 11, 2014 at 1:23 PM, Dmitry Torokhov wrote: > >> There are elements in common, but by and >> large the biggest headaches at least in large device number boots have >> already been tackled by the enterprise crowd (they don't like their >> S390's or 1024 core NUMA systems taking half an hour to come up). > > Please do not position this as a mostly solved large systems problem, > For us it is touchpad detection stalling kernel for 0.5-1 sec. Which is > a lot given that we boot in seconds. Dmitry, would working on top of the aysnc series be reasonable? Then we could address these as separate things which we'd build on top of. The one aspect I see us needing to share is the "async probe universe is OK" flag. Luis