From: Jes Sorensen <jes@trained-monkey.org>
To: Christian Hildner <christian.hildner@hob.de>
Cc: davidm@hpl.hp.com, LKML <linux-kernel@vger.kernel.org>
Subject: Re: [Linux-ia64] kmalloc() size-limitation
Date: Thu, 7 Feb 2002 10:47:33 -0500 [thread overview]
Message-ID: <15458.41366.1639.628598@trained-monkey.org> (raw)
In-Reply-To: <3C5F80F2.54AF98E3@hob.de>
In-Reply-To: <3C3D6A89.27EAA4C7@hob.de> <15421.61910.163437.45726@napali.hpl.hp.com> <3C3ED5E7.8BA479B7@hob.de> <15423.5404.65155.924018@napali.hpl.hp.com> <3C43D6EC.74B4EC85@hob.de> <d31yg1lzgm.fsf@lxplus052.cern.ch> <3C5F80F2.54AF98E3@hob.de>
>>>>> "Christian" == Christian Hildner <christian.hildner@hob.de> writes:
Christian> Jes Sorensen schrieb:
>> Because drivers needs to work on all architectures and relying on
>> different hahavior from kmalloc() is bad.
Christian> sorry for being unclear. I mean from increasing the kmalloc()
Christian> size-limit all platforms would benefit.
Thats not really a good idea, and definately not something you want to
rely on. A lot of architectures are still stuck with 4KB pages and
trying to allocate 128KB on larger in one chunk is likely to fail after
the system has been running for a while. On an ia64 with 16KB or 64KB
pages it's fairly likely it will work, but this is not necessarily a
good idea to do for other archs. If you need such a large block of
memory, vmalloc() is the real way to go.
Jes
next prev parent reply other threads:[~2002-02-07 15:48 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <3C3D6A89.27EAA4C7@hob.de>
[not found] ` <15421.61910.163437.45726@napali.hpl.hp.com>
[not found] ` <3C3ED5E7.8BA479B7@hob.de>
[not found] ` <15423.5404.65155.924018@napali.hpl.hp.com>
[not found] ` <3C43D6EC.74B4EC85@hob.de>
2002-02-04 21:16 ` [Linux-ia64] kmalloc() size-limitation Jes Sorensen
2002-02-05 6:51 ` Christian Hildner
2002-02-07 15:47 ` Jes Sorensen [this message]
2002-02-08 7:23 ` Christian Hildner
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=15458.41366.1639.628598@trained-monkey.org \
--to=jes@trained-monkey.org \
--cc=christian.hildner@hob.de \
--cc=davidm@hpl.hp.com \
--cc=linux-kernel@vger.kernel.org \
/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