On Mon, 15 Sep 2014, Joonsoo Kim wrote:
> On Thu, Sep 11, 2014 at 10:32:52PM -0400, Mikulas Patocka wrote:
> >
> >
> > On Mon, 8 Sep 2014, Christoph Lameter wrote:
> >
> > > On Mon, 8 Sep 2014, Mikulas Patocka wrote:
> > >
> > > > I don't know what you mean. If someone allocates 1 object
On Thu, Sep 11, 2014 at 10:32:52PM -0400, Mikulas Patocka wrote:
>
>
> On Mon, 8 Sep 2014, Christoph Lameter wrote:
>
> > On Mon, 8 Sep 2014, Mikulas Patocka wrote:
> >
> > > I don't know what you mean. If someone allocates 1 objects with sizes
> > > from 1 to 1, you can't have 1 sl
On Mon, 8 Sep 2014, Christoph Lameter wrote:
> On Mon, 8 Sep 2014, Mikulas Patocka wrote:
>
> > I don't know what you mean. If someone allocates 1 objects with sizes
> > from 1 to 1, you can't have 1 slab caches - you can't have a slab
> > cache for each used size. Also - you can't
On Mon, 8 Sep 2014, Mikulas Patocka wrote:
> I don't know what you mean. If someone allocates 1 objects with sizes
> from 1 to 1, you can't have 1 slab caches - you can't have a slab
> cache for each used size. Also - you can't create a slab cache in
> interrupt context.
Oh you can cr
On Mon, 8 Sep 2014, Christoph Lameter wrote:
> On Fri, 5 Sep 2014, Mikulas Patocka wrote:
>
> > This patch adds a new option DEBUG_KMALLOC that makes it possible to
> > detect writes beyond the end of space allocated with kmalloc. Normally,
> > the kmalloc function rounds the size to the next p
On Fri, 5 Sep 2014, Mikulas Patocka wrote:
> This patch adds a new option DEBUG_KMALLOC that makes it possible to
> detect writes beyond the end of space allocated with kmalloc. Normally,
> the kmalloc function rounds the size to the next power of two (there is
> exception to this rule - sizes 96
6 matches
Mail list logo