From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S964824AbcALKCx (ORCPT ); Tue, 12 Jan 2016 05:02:53 -0500 Received: from mx2.suse.de ([195.135.220.15]:38420 "EHLO mx2.suse.de" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752603AbcALKCu (ORCPT ); Tue, 12 Jan 2016 05:02:50 -0500 Message-ID: <1452592833.6017.2.camel@suse.com> Subject: Re: [PATCH v2] Add support for usbfs zerocopy. From: Oliver Neukum To: Konrad Rzeszutek Wilk Cc: "Steinar H. Gunderson" , Greg Kroah-Hartman , Lingzhu Xiang , Alan Stern , Kernel development list , USB list Date: Tue, 12 Jan 2016 11:00:33 +0100 In-Reply-To: <20160111161504.GG10641@char.us.oracle.com> References: <1452510506.3907.3.camel@suse.com> <20160111161504.GG10641@char.us.oracle.com> Content-Type: text/plain; charset="UTF-8" X-Mailer: Evolution 3.12.11 Mime-Version: 1.0 Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Mon, 2016-01-11 at 11:15 -0500, Konrad Rzeszutek Wilk wrote: > On Mon, Jan 11, 2016 at 12:08:26PM +0100, Oliver Neukum wrote: > > I suspect many drivers to be unable to deal well with a failure. > > Having this report makes "my device doesn't work" easier to solve > > as a bug report. > > > > Hence it seems to me that a driver which can handle a failure > > with a good fallback should indicate this with a flag to the > > VM layer. > > s/VM/device layer? Actually no, if a driver does something that cannot be satisfied at all, that should be logged. What we would like to go away is the log entry due to a failure to allocate memory under memory pressure or fragmentation. Regards Oliver