From: Rusty Russell <rusty@rustcorp.com.au>
To: mingo@redhat.com, davem@redhat.com
Cc: torvalds@transmeta.com, linux-kernel@vger.kernel.org,
Jens Axboe <axboe@suse.de>
Subject: [PATCH] gfp_t
Date: Thu, 26 Sep 2002 14:35:30 +1000 [thread overview]
Message-ID: <20020926044401.9C60D2C3CC@lists.samba.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 811 bytes --]
This creates a mythical gfp_t for passing gfp states, and conversion
macros __GFP() and __UNGFP(), to give warnings, It's 55k, so
compressed and attached.
[Jens, bio_alloc() has the args reversed from normal (Grrr!)]
It's worse than I'd hoped, better than I feared. I didn't find any
bugs (but then I didn't try compiling with "allyesconfig").
Notes:
o People use GFP_KERNEL instead of SLAB_KERNEL for kmem_cache_alloc,
so I changed the slab types too.
o If we really want to do this, maybe introduce gfp_t as a typedef to
int, and use it in all the interfaces first, then change the
definition later.
BTW, I'm leaving in a couple of hours, so I'm leaving this here for
someone else to get enthusiastic about 8)
Cheers,
Rusty.
--
Anyone who quotes me in their sig is an idiot. -- Rusty Russell.
[-- Attachment #2: gfp_t safety patch --]
[-- Type: application/octet-stream, Size: 13993 bytes --]
next reply other threads:[~2002-09-26 4:38 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-09-26 4:35 Rusty Russell [this message]
2002-09-26 18:59 ` [PATCH] gfp_t Rasmus Andersen
2002-09-26 19:29 ` Rasmus Andersen
2002-09-26 21:15 ` Rasmus Andersen
2002-10-15 23:10 ` Rusty Russell
2002-10-16 2:14 ` David S. Miller
2002-10-17 6:40 ` Rusty Russell
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=20020926044401.9C60D2C3CC@lists.samba.org \
--to=rusty@rustcorp.com.au \
--cc=axboe@suse.de \
--cc=davem@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--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).