All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Luck, Tony" <tony.luck@intel.com>
To: linux-ia64@vger.kernel.org
Subject: RE: __you_cannot_kmalloc_that_much
Date: Thu, 19 Jun 2003 19:03:43 +0000	[thread overview]
Message-ID: <marc-linux-ia64-105604960708951@msgid-missing> (raw)
In-Reply-To: <marc-linux-ia64-105604765306485@msgid-missing>

>   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?

Ok, I sent an e-mail to Johannes Erdfelt (with a Cc: to the
linux-usb-users mailing list) with a patch to switch the size
to a fixed 64k.

But I'm still not out of the woods ... with this patch applied
I get a:

undefined reference to `local symbols in discarded section .exit.text'

message.  Is this related to the warning about using an old linker?

gcc: 3.2
as: GNU assembler version 2.13.90
ld: GNU ld version 2.13.90.0.2 20020802

-Tony

  parent reply	other threads:[~2003-06-19 19:03 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 ` __you_cannot_kmalloc_that_much David Mosberger
2003-06-19 19:03 ` Luck, Tony [this message]
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-105604960708951@msgid-missing \
    --to=tony.luck@intel.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 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.