From: Christian Hildner <christian.hildner@hob.de>
To: Jes Sorensen <jes@sunsite.dk>
Cc: davidm@hpl.hp.com, LKML <linux-kernel@vger.kernel.org>
Subject: Re: [Linux-ia64] kmalloc() size-limitation
Date: Tue, 05 Feb 2002 07:51:30 +0100 [thread overview]
Message-ID: <3C5F80F2.54AF98E3@hob.de> (raw)
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>
Jes Sorensen schrieb:
> Christian Hildner <christian.hildner@hob.de> writes:
>
> > David,
> >
> > you proposed me to use alloc_pages() instead of kmalloc() in order
> > to get memory bigger than the 128K limit of the kmalloc() call. But
> > even driver-developers don't want to handle with the page struct
> > unless this is unavoidable. Which are the disadvantages of
> > increasing the size limit of kmalloc() to 256K, 512K or 1M since
> > machines are getting bigger and 64Bit machines break with current
> > memory limitations?
>
> Because drivers needs to work on all architectures and relying on
> different hahavior from kmalloc() is bad.
>
> Jes
Jes,
sorry for being unclear. I mean from increasing the kmalloc() size-limit
all platforms would benefit.
Christian
PS: David, I am looking forward getting your book. You are doing a great
job.
next prev parent reply other threads:[~2002-02-05 7:01 UTC|newest]
Thread overview: 7+ 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 [this message]
2002-02-07 15:47 ` Jes Sorensen
2002-02-08 7:23 ` Christian Hildner
2002-01-15 7:14 Christian Hildner
2002-01-15 7:56 ` Tang, Yu
2002-02-04 21:16 ` Jes Sorensen
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=3C5F80F2.54AF98E3@hob.de \
--to=christian.hildner@hob.de \
--cc=davidm@hpl.hp.com \
--cc=jes@sunsite.dk \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.