From: Manfred Spraul <manfred@colorfullife.com>
To: Alan Cox <alan@lxorguk.ukuu.org.uk>
Cc: David Weinehall <tao@acc.umu.se>,
Jeff Garzik <jgarzik@mandrakesoft.com>,
Nick Urbanik <nicku@vtc.edu.hk>,
Kernel list <linux-kernel@vger.kernel.org>
Subject: Re: 2.4.2-pre3 compile error in 6pack.c
Date: Sun, 11 Feb 2001 22:09:31 +0100 [thread overview]
Message-ID: <3A86FF8B.FD422B54@colorfullife.com> (raw)
In-Reply-To: <E14S3KC-0004yo-00@the-village.bc.nu>
Alan Cox wrote:
>
> > Do you really prefer if drivers contain a
> >
> > static inline void* safe_kmalloc(size, flags)
> > {
> > if(size > LIMIT)
> > return NULL;
> > return kmalloc(size, flags);
> > }
>
> It isnt that simple. Look at af_unix.c for example. It needs to know the
> maximum safe request size to set values up and is prepared to accept
> smaller values if that fails
>
Ok, I just downloaded -ac9.
Hmm.
What about removing -16 instead of increasing it to 64?
The slab allocator is perfect for power of 2 allocations!
The slab descriptors are stored outside in seperate buffers.
And why KMALLOC_SIZE/2?
"Keep 2 messages in ..."?
Btw, sock_alloc_send_skb() (net/core.c) still uses the wrong allocation
mode for "size":
GFP_BUFFER both sleeps and uses the atomic queue.
skb = alloc_skb(size, sk->allocation & (~__GFP_WAIT));
--
Manfred
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
Please read the FAQ at http://www.tux.org/lkml/
prev parent reply other threads:[~2001-02-11 21:09 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-02-11 12:37 2.4.2-pre3 compile error in 6pack.c Nick Urbanik
2001-02-11 17:14 ` Alan Cox
2001-02-11 19:59 ` Jeff Garzik
2001-02-11 20:08 ` David Weinehall
2001-02-11 20:14 ` Jeff Garzik
2001-02-11 20:25 ` Manfred Spraul
2001-02-11 20:33 ` Alan Cox
2001-02-11 20:30 ` Alan Cox
2001-02-11 20:39 ` Manfred Spraul
2001-02-11 20:42 ` Alan Cox
2001-02-11 21:09 ` Manfred Spraul [this message]
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=3A86FF8B.FD422B54@colorfullife.com \
--to=manfred@colorfullife.com \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=jgarzik@mandrakesoft.com \
--cc=linux-kernel@vger.kernel.org \
--cc=nicku@vtc.edu.hk \
--cc=tao@acc.umu.se \
/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