All of lore.kernel.org
 help / color / mirror / Atom feed
From: Timur Tabi <ttabi@interactivesi.com>
To: linux-kernel@vger.kernel.org
Subject: Re: kmalloc() of 4MB causes "kernel BUG at slab.c:1542!"
Date: Wed, 17 Jan 2001 14:39:57 -0600	[thread overview]
Message-ID: <20010117204044Z130643-403+1272@vger.kernel.org> (raw)
In-Reply-To: <20010117121719.A29786@skull.piratehaven.org>
In-Reply-To: <20010117135420.A3536@remotepoint.com> <20010117135420.A3536@remotepoint.com>  ; from rick@remotepoint.com on Wed, Jan 17, 2001 at 01:54:20PM -0600

** Reply to message from Brian Pomerantz <bapper@piratehaven.org> on Wed, 17
Jan 2001 12:17:19 -0800


> The most you can kmalloc() is 128KB unless this has changed in the 2.4
> kernel which I doubt.  If you want a region of memory that large, use
> vmalloc().  Of course, this doesn't guarantee a contiguous region.

Couldn't you also use get_free_pages (commonly abbreviated as "gfp")?  You can
alloc up to 2MB chunks on an x86 I think.


-- 
Timur Tabi - ttabi@interactivesi.com
Interactive Silicon - http://www.interactivesi.com

When replying to a mailing-list message, please direct the reply to the mailing list only.  Don't send another copy to me.
-
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/

  parent reply	other threads:[~2001-01-17 20:41 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-01-17 19:54 kmalloc() of 4MB causes "kernel BUG at slab.c:1542!" Rick Richardson
2001-01-17 20:17 ` Brian Pomerantz
2001-01-17 20:39 ` Timur Tabi [this message]
2001-01-18  5:11 ` Hans Grobler

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=20010117204044Z130643-403+1272@vger.kernel.org \
    --to=ttabi@interactivesi.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 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.