public inbox for linux-ia64@vger.kernel.org
 help / color / mirror / Atom feed
From: David Mosberger <davidm@napali.hpl.hp.com>
To: linux-ia64@vger.kernel.org
Subject: Re: __you_cannot_kmalloc_that_much
Date: Thu, 19 Jun 2003 18:38:47 +0000	[thread overview]
Message-ID: <marc-linux-ia64-105604795606878@msgid-missing> (raw)
In-Reply-To: <marc-linux-ia64-105604765306485@msgid-missing>

>>>>> On Thu, 19 Jun 2003 11:33:59 -0700, "Luck, Tony" <tony.luck@intel.com> said:

  Tony> While trying to compile the latest pull from
  Tony> the lia64.bkbits.net:8080/linux-ia64-2.5
  Tony> repository I hit the "you_cannot_kmalloc_that_much"
  Tony> message in the final link.

  Tony> The culprit is in

  Tony> drivers/usb/host/uhci-debug.c

  Tony> which contains:

  Tony> #define MAX_OUTPUT      (PAGE_SIZE * 16)

  Tony> ...

  up-> data = kmalloc(MAX_OUTPUT, GFP_KERNEL);

  Tony> With the default 16k page size we are trying to
  Tony> allocate 256K of memory, which is bigger that the
  Tony> largest size pool in include/linux/kmalloc_sizes.h


  Tony> Do we need a larger pool (I don't think so) or is
  Tony> this allocation excessive?

Clearly the latter.  If it works with 4KB page size on x86, certainly
we don't need 4 or 8 times more space on ia64.

Can you take this up directly with the author of the offending line?

Thanks,

	--david

  reply	other threads:[~2003-06-19 18:38 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-06-19 18:33 __you_cannot_kmalloc_that_much Luck, Tony
2003-06-19 18:38 ` David Mosberger [this message]
2003-06-19 19:03 ` __you_cannot_kmalloc_that_much Luck, Tony
2003-06-19 19:15 ` __you_cannot_kmalloc_that_much David Mosberger

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=marc-linux-ia64-105604795606878@msgid-missing \
    --to=davidm@napali.hpl.hp.com \
    --cc=linux-ia64@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