From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1752091AbbEAUtc (ORCPT ); Fri, 1 May 2015 16:49:32 -0400 Received: from mga03.intel.com ([134.134.136.65]:57677 "EHLO mga03.intel.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751233AbbEAUt2 convert rfc822-to-8bit (ORCPT ); Fri, 1 May 2015 16:49:28 -0400 X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="5.13,352,1427785200"; d="scan'208";a="488242743" From: "Drokin, Oleg" To: "Simmons, James A." CC: Julia Lawall , "devel@driverdev.osuosl.org" , Greg Kroah-Hartman , "kernel-janitors@vger.kernel.org" , "linux-kernel@vger.kernel.org" , "HPDD-discuss@lists.01.org" Subject: Re: [HPDD-discuss] [PATCH 2/11] Staging: lustre: fld: Use kzalloc and kfree Thread-Topic: [HPDD-discuss] [PATCH 2/11] Staging: lustre: fld: Use kzalloc and kfree Thread-Index: AQHQhDcX/Si4kRb33kqKwqEINQFc2Z1oBQQAgAAIhIA= Date: Fri, 1 May 2015 20:49:26 +0000 Message-ID: References: <1430495482-933-1-git-send-email-Julia.Lawall@lip6.fr> <1430495482-933-11-git-send-email-Julia.Lawall@lip6.fr> <524505df3433441494cf082a425f2ee7@EXCHCS32.ornl.gov> In-Reply-To: <524505df3433441494cf082a425f2ee7@EXCHCS32.ornl.gov> Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: x-originating-ip: [10.252.199.128] Content-Type: text/plain; charset="us-ascii" Content-ID: Content-Transfer-Encoding: 8BIT MIME-Version: 1.0 Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On May 1, 2015, at 4:18 PM, Simmons, James A. wrote: > Yes the LARGE functions do the switching. I was expecting also patches to remove the > OBD_ALLOC_LARGE functions as well which is not the case here. I do have one question still. The > macro __OBD_MALLOC_VERBOSE allowed the ability to simulate memory allocation failures at > a certain percentage rate. Does something exist in the kernel to duplicate that functionality? > Once these macros are gone we lose the ability to simulate high memory allocation failures. Yes, there are things like https://lkml.org/lkml/2014/12/25/64 So I think the API is even riher compared to what our old wrapper code was able to do. Bye, Oleg