From: Denis Vlasenko <vda@port.imtp.ilyichevsk.odessa.ua>
To: Ingo Molnar <mingo@elte.hu>, Rusty Russell <rusty@rustcorp.com.au>
Cc: Linus Torvalds <torvalds@transmeta.com>, <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] streq()
Date: Tue, 24 Sep 2002 11:07:58 -0200 [thread overview]
Message-ID: <200209240813.g8O8DWp24815@Port.imtp.ilyichevsk.odessa.ua> (raw)
In-Reply-To: <Pine.LNX.4.44.0209240731060.8824-100000@localhost.localdomain>
On 24 September 2002 03:40, Ingo Molnar wrote:
> On Tue, 24 Sep 2002, Rusty Russell wrote:
> there's a few more places that tend to cause wasted time, no matter what:
> - kmalloc(size, flags)/gfp(order, flags) argument ordering. A few months
> ago i wasted two days on such a bug - since 'size' was very small
> usually, it never showed up that the allocated buffer was short, until
> some rare load-test increased the 'size'.
Aughment kmalloc(size, GFP_XXXXX) with kmalloc_XXXXX(size) (inline of course)?
You may use this form in those 90% cases where flags are constant.
This also gets rid of GFP_ prefixes (shorter).
Ingo, Rusty?
--
vda
--- linux-2.5.36/include/linux/slab.h.orig Tue Sep 24 11:00:42 2002
+++ linux-2.5.36/include/linux/slab.h Tue Sep 24 11:06:32 2002
@@ -61,6 +61,15 @@
extern void *kmalloc(size_t, int);
extern void kfree(const void *);
+extern inline void *kmalloc_NOHIGHIO(size_t sz) { return kmalloc(sz, GFP_NOHIGHIO); }
+extern inline void *kmalloc_NOIO (size_t sz) { return kmalloc(sz, GFP_NOIO ); }
+extern inline void *kmalloc_NOFS (size_t sz) { return kmalloc(sz, GFP_NOFS ); }
+extern inline void *kmalloc_ATOMIC (size_t sz) { return kmalloc(sz, GFP_ATOMIC ); }
+extern inline void *kmalloc_USER (size_t sz) { return kmalloc(sz, GFP_USER ); }
+extern inline void *kmalloc_HIGHUSER(size_t sz) { return kmalloc(sz, GFP_HIGHUSER); }
+extern inline void *kmalloc_KERNEL (size_t sz) { return kmalloc(sz, GFP_KERNEL ); }
+extern inline void *kmalloc_NFS (size_t sz) { return kmalloc(sz, GFP_NFS ); }
+extern inline void *kmalloc_KSWAPD (size_t sz) { return kmalloc(sz, GFP_KSWAPD ); }
extern int FASTCALL(kmem_cache_reap(int));
next prev parent reply other threads:[~2002-09-24 8:13 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-09-24 4:49 [PATCH] streq() Rusty Russell
2002-09-24 5:40 ` Ingo Molnar
2002-09-24 6:04 ` Rusty Russell
2002-09-24 6:24 ` David S. Miller
2002-09-24 7:28 ` Rusty Russell
2002-09-24 7:38 ` Ingo Molnar
2002-09-24 8:19 ` David S. Miller
2002-09-24 13:07 ` Denis Vlasenko [this message]
2002-09-24 17:21 ` H. Peter Anvin
2002-09-25 11:27 ` Daniel Egger
2002-09-25 11:45 ` Russell King
2002-09-25 12:38 ` Daniel Egger
2002-09-25 12:19 ` Michael Sinz
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=200209240813.g8O8DWp24815@Port.imtp.ilyichevsk.odessa.ua \
--to=vda@port.imtp.ilyichevsk.odessa.ua \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=rusty@rustcorp.com.au \
--cc=torvalds@transmeta.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;
as well as URLs for NNTP newsgroup(s).