[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <5ACF44E8-AB92-4343-88CA-C32DA6D6F6CE@intel.com>
Date: Tue, 23 Jun 2015 08:30:13 +0000
From: "Drokin, Oleg" <oleg.drokin@...el.com>
To: Julia Lawall <Julia.Lawall@...6.fr>
CC: "Dilger, Andreas" <andreas.dilger@...el.com>,
Greg Kroah-Hartman <gregkh@...uxfoundation.org>,
"<HPDD-discuss@...ts.01.org>" <HPDD-discuss@...1.01.org>,
"<devel@...verdev.osuosl.org>" <devel@...verdev.osuosl.org>,
"<linux-kernel@...r.kernel.org>" <linux-kernel@...r.kernel.org>
Subject: Re: lustre: LIBCFS_ALLOC
On Jun 23, 2015, at 2:23 AM, Julia Lawall wrote:
> It seems that libcfs_kvzalloc doesn't use any particular threshold or
> switchingbetween kzalloc and vmalloc, so can be replaced by ths function
> too?
If you mean to replace all instances of LIBCFS_ALLOC with libcfs_kvzalloc (and all frees with kvfree) then yes, that could be done I think.
Bye,
Oleg--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists