All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jesper Dangaard Brouer <brouer@redhat.com>
To: Christoph Lameter <cl@linux.com>
Cc: linux-kernel@vger.kernel.org, linux-mm@kvack.org,
	akpm@linuxfoundation.org, Pekka Enberg <penberg@kernel.org>,
	iamjoonsoo@lge.com, brouer@redhat.com
Subject: Re: Slab infrastructure for bulk object allocation and freeing V2
Date: Tue, 31 Mar 2015 13:17:55 +1300	[thread overview]
Message-ID: <20150331131755.5dd5f69a@redhat.com> (raw)
In-Reply-To: <alpine.DEB.2.11.1503300927290.6646@gentwo.org>

On Mon, 30 Mar 2015 09:31:19 -0500 (CDT)
Christoph Lameter <cl@linux.com> wrote:

> After all of the earlier discussions I thought it would be better to
> first get agreement on the basic way to allow implementation of the
> bulk alloc in the common slab code. So this is a revision of the initial
> proposal and it just covers the first patch.

I agree, it would be good to get the basic API in.
 
> This patch adds the basic infrastructure for alloc / free operations
> on pointer arrays. It includes a generic function in the common
> slab code that is used in this infrastructure patch to
> create the unoptimized functionality for slab bulk operations.
> 
> Allocators can then provide optimized allocation functions
> for situations in which large numbers of objects are needed.
> These optimization may avoid taking locks repeatedly and
> bypass metadata creation if all objects in slab pages
> can be used to provide the objects required.

I'll volunteer to performance benchmark the different allocators
optimized functions in this area. (I'll have time after April 13th).

 
> Signed-off-by: Christoph Lameter <cl@linux.com>

Acked-by: Jesper Dangaard Brouer <brouer@redhat.com>
 
-- 
Best regards,
  Jesper Dangaard Brouer
  MSc.CS, Sr. Network Kernel Developer at Red Hat
  Author of http://www.iptv-analyzer.org
  LinkedIn: http://www.linkedin.com/in/brouer

--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org.  For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>

WARNING: multiple messages have this Message-ID (diff)
From: Jesper Dangaard Brouer <brouer@redhat.com>
To: Christoph Lameter <cl@linux.com>
Cc: linux-kernel@vger.kernel.org, linux-mm@kvack.org,
	akpm@linuxfoundation.org, Pekka Enberg <penberg@kernel.org>,
	iamjoonsoo@lge.com, brouer@redhat.com
Subject: Re: Slab infrastructure for bulk object allocation and freeing V2
Date: Tue, 31 Mar 2015 13:17:55 +1300	[thread overview]
Message-ID: <20150331131755.5dd5f69a@redhat.com> (raw)
In-Reply-To: <alpine.DEB.2.11.1503300927290.6646@gentwo.org>

On Mon, 30 Mar 2015 09:31:19 -0500 (CDT)
Christoph Lameter <cl@linux.com> wrote:

> After all of the earlier discussions I thought it would be better to
> first get agreement on the basic way to allow implementation of the
> bulk alloc in the common slab code. So this is a revision of the initial
> proposal and it just covers the first patch.

I agree, it would be good to get the basic API in.
 
> This patch adds the basic infrastructure for alloc / free operations
> on pointer arrays. It includes a generic function in the common
> slab code that is used in this infrastructure patch to
> create the unoptimized functionality for slab bulk operations.
> 
> Allocators can then provide optimized allocation functions
> for situations in which large numbers of objects are needed.
> These optimization may avoid taking locks repeatedly and
> bypass metadata creation if all objects in slab pages
> can be used to provide the objects required.

I'll volunteer to performance benchmark the different allocators
optimized functions in this area. (I'll have time after April 13th).

 
> Signed-off-by: Christoph Lameter <cl@linux.com>

Acked-by: Jesper Dangaard Brouer <brouer@redhat.com>
 
-- 
Best regards,
  Jesper Dangaard Brouer
  MSc.CS, Sr. Network Kernel Developer at Red Hat
  Author of http://www.iptv-analyzer.org
  LinkedIn: http://www.linkedin.com/in/brouer

  reply	other threads:[~2015-03-31  0:18 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-03-30 14:31 Slab infrastructure for bulk object allocation and freeing V2 Christoph Lameter
2015-03-30 14:31 ` Christoph Lameter
2015-03-31  0:17 ` Jesper Dangaard Brouer [this message]
2015-03-31  0:17   ` Jesper Dangaard Brouer
2015-03-31 21:20 ` Andrew Morton
2015-03-31 21:20   ` Andrew Morton
2015-04-02 14:25   ` Christoph Lameter
2015-04-02 14:25     ` Christoph Lameter
2015-04-02 20:42     ` Andrew Morton
2015-04-02 20:42       ` Andrew Morton
2015-04-06 18:27       ` Christoph Lameter
2015-04-06 18:27         ` Christoph Lameter

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20150331131755.5dd5f69a@redhat.com \
    --to=brouer@redhat.com \
    --cc=akpm@linuxfoundation.org \
    --cc=cl@linux.com \
    --cc=iamjoonsoo@lge.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=penberg@kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.