All of lore.kernel.org
 help / color / mirror / Atom feed
From: David Miller <davem@davemloft.net>
To: clameter@sgi.com
Cc: hugh@veritas.com, James.Bottomley@steeleye.com,
	rmk+lkml@arm.linux.org.uk, akpm@linux-foundation.org,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH] Containment measures for slab objects on scatter gather lists
Date: Thu, 28 Jun 2007 21:10:13 -0700 (PDT)	[thread overview]
Message-ID: <20070628.211013.74747656.davem@davemloft.net> (raw)
In-Reply-To: <Pine.LNX.4.64.0706282047160.10035@schroedinger.engr.sgi.com>

From: Christoph Lameter <clameter@sgi.com>
Date: Thu, 28 Jun 2007 21:01:36 -0700 (PDT)

> Modify the functions in the affected arches to check for PageSlab() and 
> use a NULL mapping if such a page is encountered. This may only be 
> necessary for parisc and arm since sparc64 and xtensa do not scan over 
> processes mapping a page but I have modified those two arches also for 
> correctnesses sake since they use page_mapping() in flush_dcache_page().
> 
> Still a better solution would be to not use the slab allocator at all for 
> the objects that are used to send commands to the devices. These are not 
> permanent and grabbing a page from the pcp lists and putting it back is 
> likely as fast as performing a kmalloc.

Jens Axboe wants to get references to the page structs behind
kmalloc() allocated pages in his networking splice work.

We pass scatterlists around, but networking buffers are
composed of a kmalloc()'d data header area for packet headers
and some of the initial packet data, then a true scatterlist
of page/offset/len triplets.

Splice wants to work with pages everwhere.

This is a reocurring theme, we should provide some kind of
solution to these issues instead of wishing they would go
away.

We could make a special allocator in the networking that carves
chunks out of pages but I'm sure you'll find that about as stupid
and wasteful as I do :-)


  reply	other threads:[~2007-06-29  4:10 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-06-29  4:01 [PATCH] Containment measures for slab objects on scatter gather lists Christoph Lameter
2007-06-29  4:10 ` David Miller [this message]
2007-06-29  4:22   ` Christoph Lameter
2007-06-29  4:28     ` David Miller
2007-06-29  4:39       ` Christoph Lameter
2007-06-29  5:06         ` David Miller
2007-06-29  5:24           ` Andrew Morton
2007-06-29  5:37             ` David Miller
2007-06-29  5:45               ` Andrew Morton
2007-06-29  6:51                 ` Christoph Lameter
2007-06-29 12:16                 ` Alan Cox
2007-06-29 20:45                   ` Andrew Morton
2007-06-29 21:14                     ` Russell King
2007-06-29 23:11                       ` Alan Cox
2007-06-30  7:54                         ` Russell King
2007-06-29 22:39                     ` Alan Cox
2007-06-29  6:50               ` Christoph Lameter
2007-06-30  8:49             ` Christoph Hellwig
2007-06-29  7:00           ` Christoph Lameter
2007-06-29  9:06             ` David Miller
2007-06-29 13:04 ` Hugh Dickins
2007-06-29 14:15   ` 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=20070628.211013.74747656.davem@davemloft.net \
    --to=davem@davemloft.net \
    --cc=James.Bottomley@steeleye.com \
    --cc=akpm@linux-foundation.org \
    --cc=clameter@sgi.com \
    --cc=hugh@veritas.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=rmk+lkml@arm.linux.org.uk \
    /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.