On 08/04/2018 02:28 AM, Geert Uytterhoeven wrote:
On Sat, Aug 4, 2018 at 12:34 AM Matthew Wilcox wrote:
On Fri, Aug 03, 2018 at 02:22:57PM -0700, Guenter Roeck wrote:
On Thu, Apr 12, 2018 at 12:13:22PM -0700, Matthew Wilcox wrote:
From: Matthew Wilcox
__GFP_ZERO requests that the object be i
On Sat, Aug 4, 2018 at 12:34 AM Matthew Wilcox wrote:
> On Fri, Aug 03, 2018 at 02:22:57PM -0700, Guenter Roeck wrote:
> > On Thu, Apr 12, 2018 at 12:13:22PM -0700, Matthew Wilcox wrote:
> > > From: Matthew Wilcox
> > > __GFP_ZERO requests that the object be initialised to all-zeroes,
> > > while
On Fri, Aug 03, 2018 at 02:22:57PM -0700, Guenter Roeck wrote:
> Hi,
>
> On Thu, Apr 12, 2018 at 12:13:22PM -0700, Matthew Wilcox wrote:
> > From: Matthew Wilcox
> >
> > __GFP_ZERO requests that the object be initialised to all-zeroes,
> > while the purpose of a constructor is to initialise an o
Hi,
On Thu, Apr 12, 2018 at 12:13:22PM -0700, Matthew Wilcox wrote:
> From: Matthew Wilcox
>
> __GFP_ZERO requests that the object be initialised to all-zeroes,
> while the purpose of a constructor is to initialise an object to a
> particular pattern. We cannot do both. Add a warning to catch
On Thu, 12 Apr 2018, Matthew Wilcox wrote:
> __GFP_ZERO requests that the object be initialised to all-zeroes,
> while the purpose of a constructor is to initialise an object to a
> particular pattern. We cannot do both. Add a warning to catch any
> users who mistakenly pass a __GFP_ZERO flag wh
From: Matthew Wilcox
__GFP_ZERO requests that the object be initialised to all-zeroes,
while the purpose of a constructor is to initialise an object to a
particular pattern. We cannot do both. Add a warning to catch any
users who mistakenly pass a __GFP_ZERO flag when allocating a slab with
a c
6 matches
Mail list logo
