linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: "Luiz Fernando N. Capitulino" <lcapitulino@mandriva.com.br>
To: Nick Piggin <npiggin@suse.de>
Cc: Christoph Lameter <clameter@sgi.com>,
	Linux Memory Management List <linux-mm@kvack.org>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: [rfc] SLQB: YASA
Date: Tue, 8 Apr 2008 15:51:42 -0300	[thread overview]
Message-ID: <20080408155142.4b421497@mandriva.com.br> (raw)
In-Reply-To: <20080408115717.GB22687@wotan.suse.de>

Em Tue, 8 Apr 2008 13:57:17 +0200
Nick Piggin <npiggin@suse.de> escreveu:

| Here is my more working version of SLQB. 
| 
| Was experimenting with a couple of different ways to do remote freeing,
| but it is really hard to tune properly without having "real" workloads,
| due to cache effects.
| 
| Anyway, same comments apply. Patch is against mainline.

 I get the following error when compiling without CONFIG_SMP

"""
In file included from include/linux/rcupdate.h:52,
                 from include/linux/slqb_def.h:15,
                 from include/linux/slab.h:121,
                 from include/asm/pgtable_32.h:22,
                 from include/asm/pgtable.h:241,
                 from include/linux/mm.h:40,
                 from arch/x86/kernel/pci-dma_32.c:12:
include/linux/percpu.h: In function '__percpu_alloc_mask':
include/linux/percpu.h:106: error: implicit declaration of function 'kzalloc'
include/linux/percpu.h:106: warning: return makes pointer from integer without a cast
In file included from include/asm/pgtable_32.h:22,
                 from include/asm/pgtable.h:241,
                 from include/linux/mm.h:40,
                 from arch/x86/kernel/pci-dma_32.c:12:
include/linux/slab.h: At top level:
include/linux/slab.h:272: error: conflicting types for 'kzalloc'
include/linux/percpu.h:106: error: previous implicit declaration of 'kzalloc' was here
ICECC[27645] 15:49:30: Compiled on XXXXXXXX
make[1]: *** [arch/x86/kernel/pci-dma_32.o] Error 1
make: *** [arch/x86/kernel] Error 2

"""

 Could not figure out what the problem is.

 Regarding performance tests, I saw that Christoph has some
interesting test modules in his git repository. Do you think it's
worth to run them?

-- 
Luiz Fernando N. Capitulino

--
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>

  reply	other threads:[~2008-04-08 18:51 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-04-03  7:25 Nick Piggin
2008-04-03  7:45 ` Pekka Enberg
2008-04-03  7:57   ` Nick Piggin
2008-04-03  8:13     ` Nick Piggin
2008-04-03  8:24       ` Pekka Enberg
2008-04-03  8:32         ` Nick Piggin
2008-04-03  8:17     ` KOSAKI Motohiro
2008-04-03  8:26       ` Nick Piggin
2008-04-03  8:33         ` KOSAKI Motohiro
2008-04-03  8:41         ` Andi Kleen
2008-04-03 14:23 ` Nick Piggin
2008-04-03 19:04   ` Luiz Fernando N. Capitulino
2008-04-03 19:12 ` Christoph Lameter
2008-04-08 11:57   ` Nick Piggin
2008-04-08 18:51     ` Luiz Fernando N. Capitulino [this message]
2008-04-09  2:10       ` Nick Piggin

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=20080408155142.4b421497@mandriva.com.br \
    --to=lcapitulino@mandriva.com.br \
    --cc=clameter@sgi.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=npiggin@suse.de \
    /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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox