From: Nikita Danilov <Nikita@Namesys.COM>
To: Manfred Spraul <manfred@colorfullife.com>
Cc: Alan Cox <alan@lxorguk.ukuu.org.uk>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH,RFC] faster kmalloc lookup
Date: Mon, 28 Oct 2002 16:05:27 +0300 [thread overview]
Message-ID: <15805.13847.945978.673664@laputa.namesys.com> (raw)
In-Reply-To: <3DBBEA2F.6000404@colorfullife.com>
Manfred Spraul writes:
> I've run my slab microbenchmark over the 3 versions:
> - current
> - generic_fls
> - i386 asm optimized fls
>
> The test reports the fastest time for 100 kmalloc calls in a tight loop
> (Duron 700). Loop/test overhead substracted.
>
> 32-byte alloc:
> current: 41 ticks
> generic_fls: 56 ticks
> bsrl: 54 ticks
>
> 4096 byte alloc: 84 ticks
> generic_fls: 53 ticks
> bsrl: 54 ticks
>
> 40 ticks difference for -current between 4096 and 32 bytes - ~4 cycles
> for each loop.
> bit scan is 10 ticks slower for 32 byte allocs, 30 ticks faster for 4096
> byte allocs.
>
> No difference between generic_fls and bsrl - the branch predictor can
> easily predict all branches in generic_fls for constant kmalloc calls.
>
Most kmalloc calls get constant size argument (usually
sizeof(something)). So, if switch() is used in stead of loop (and
kmalloc made inline), compiler would be able to optimize away
cache_sizes[] selection completely. Attached (ugly) patch does this.
> --
Nikita.
===== include/linux/slab.h 1.13 vs edited =====
--- 1.13/include/linux/slab.h Thu Sep 26 04:41:05 2002
+++ edited/include/linux/slab.h Mon Oct 28 15:55:35 2002
@@ -58,8 +58,91 @@
extern void kmem_cache_free(kmem_cache_t *, void *);
extern unsigned int kmem_cache_size(kmem_cache_t *);
-extern void *kmalloc(size_t, int);
extern void kfree(const void *);
+extern void * __kmalloc (int i, size_t size, int flags);
+
+/**
+ * kmalloc - allocate memory
+ * @size: how many bytes of memory are required.
+ * @flags: the type of memory to allocate.
+ *
+ * kmalloc is the normal method of allocating memory
+ * in the kernel.
+ *
+ * The @flags argument may be one of:
+ *
+ * %GFP_USER - Allocate memory on behalf of user. May sleep.
+ *
+ * %GFP_KERNEL - Allocate normal kernel ram. May sleep.
+ *
+ * %GFP_ATOMIC - Allocation will not sleep. Use inside interrupt handlers.
+ *
+ * Additionally, the %GFP_DMA flag may be set to indicate the memory
+ * must be suitable for DMA. This can mean different things on different
+ * platforms. For example, on i386, it means that the memory must come
+ * from the first 16MB.
+ */
+static inline void * kmalloc (size_t size, int flags)
+{
+ int i;
+
+ switch(size) {
+#if PAGE_SIZE == 4096
+ case 0 ... 32:
+ i = 0;
+ break;
+ case 33 ... 64:
+#else
+ case 0 ... 64:
+#endif
+ i = 1;
+ break;
+ case 65 ... 96:
+ i = 2;
+ break;
+ case 97 ... 128:
+ i = 3;
+ break;
+ case 129 ... 192:
+ i = 4;
+ break;
+ case 193 ... 256:
+ i = 5;
+ break;
+ case 257 ... 512:
+ i = 6;
+ break;
+ case 513 ... 1024:
+ i = 7;
+ break;
+ case 1025 ... 2048:
+ i = 8;
+ break;
+ case 2049 ... 4096:
+ i = 9;
+ break;
+ case 4097 ... 8192:
+ i = 10;
+ break;
+ case 8193 ... 16384:
+ i = 11;
+ break;
+ case 16385 ... 32768:
+ i = 12;
+ break;
+ case 32769 ... 65536:
+ i = 13;
+ break;
+ case 65537 ... 131072:
+ i = 14;
+ break;
+ default:
+ return NULL;
+ }
+
+ return __kmalloc(i, size, flags);
+}
+
extern int FASTCALL(kmem_cache_reap(int));
===== mm/slab.c 1.33 vs edited =====
--- 1.33/mm/slab.c Sat Sep 28 18:23:50 2002
+++ edited/mm/slab.c Mon Oct 28 16:01:24 2002
@@ -1573,40 +1573,6 @@
}
/**
- * kmalloc - allocate memory
- * @size: how many bytes of memory are required.
- * @flags: the type of memory to allocate.
- *
- * kmalloc is the normal method of allocating memory
- * in the kernel.
- *
- * The @flags argument may be one of:
- *
- * %GFP_USER - Allocate memory on behalf of user. May sleep.
- *
- * %GFP_KERNEL - Allocate normal kernel ram. May sleep.
- *
- * %GFP_ATOMIC - Allocation will not sleep. Use inside interrupt handlers.
- *
- * Additionally, the %GFP_DMA flag may be set to indicate the memory
- * must be suitable for DMA. This can mean different things on different
- * platforms. For example, on i386, it means that the memory must come
- * from the first 16MB.
- */
-void * kmalloc (size_t size, int flags)
-{
- cache_sizes_t *csizep = cache_sizes;
-
- for (; csizep->cs_size; csizep++) {
- if (size > csizep->cs_size)
- continue;
- return __kmem_cache_alloc(flags & GFP_DMA ?
- csizep->cs_dmacachep : csizep->cs_cachep, flags);
- }
- return NULL;
-}
-
-/**
* kmem_cache_free - Deallocate an object
* @cachep: The cache the allocation was from.
* @objp: The previously allocated object.
@@ -1626,6 +1592,19 @@
local_irq_save(flags);
__kmem_cache_free(cachep, objp);
local_irq_restore(flags);
+}
+
+void * __kmalloc (int i, size_t size, int flags)
+{
+ cache_sizes_t *csizep;
+
+#if PAGE_SIZE == 4096
+ csizep = &cache_sizes[i];
+#else
+ csizep = &cache_sizes[i - 1];
+#endif
+ return kmem_cache_alloc(flags & GFP_DMA ?
+ csizep->cs_dmacachep : csizep->cs_cachep, flags);
}
/**
next prev parent reply other threads:[~2002-10-28 12:59 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-10-26 19:22 Manfred Spraul
2002-10-26 22:30 ` Alan Cox
2002-10-27 10:08 ` Manfred Spraul
2002-10-27 13:29 ` Manfred Spraul
2002-10-28 13:05 ` Nikita Danilov [this message]
2002-10-28 13:18 ` Marcus Alanen
2002-10-28 13:26 ` Nikita Danilov
2002-10-28 16:03 ` Manfred Spraul
2002-10-31 9:35 ` Arjan van de Ven
2002-10-31 23:03 ` Manfred Spraul
[not found] <3DBAEB64.1090109@colorfullife.com.suse.lists.linux.kernel>
[not found] ` <1036056917.2872.0.camel@dhcp59-228.rdu.redhat.com.suse.lists.linux.kernel>
[not found] ` <3DC1B6D0.8050202@colorfullife.com.suse.lists.linux.kernel>
2002-11-01 8:03 ` Andi Kleen
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=15805.13847.945978.673664@laputa.namesys.com \
--to=nikita@namesys.com \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=linux-kernel@vger.kernel.org \
--cc=manfred@colorfullife.com \
/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
all inboxes | Powered by JetHome®