From: Arnaldo Carvalho de Melo <acme@conectiva.com.br>
To: Anton Altaparmakov <aia21@cam.ac.uk>
Cc: "Michael Nguyen" <mnguyen@ariodata.com>,
"David S. Miller" <davem@redhat.com>,
"Petko Manolov" <pmanolov@Lnxw.COM>,
<linux-kernel@vger.kernel.org>
Subject: Re: RE2: kmalloc
Date: Fri, 15 Jun 2001 15:46:59 -0300 [thread overview]
Message-ID: <20010615154659.A942@conectiva.com.br> (raw)
In-Reply-To: <8A098FDFC6EED94B872CA2033711F86F01A9A2@orion.ariodata.com> <8A098FDFC6EED94B872CA2033711F86F01A9A2@orion.ariodata.com> <20010615145856.C960@conectiva.com.br> <5.1.0.14.2.20010615192508.00afe540@pop.cus.cam.ac.uk>
In-Reply-To: <5.1.0.14.2.20010615192508.00afe540@pop.cus.cam.ac.uk>; from aia21@cam.ac.uk on Fri, Jun 15, 2001 at 07:26:16PM +0100
Em Fri, Jun 15, 2001 at 07:26:16PM +0100, Anton Altaparmakov escreveu:
> At 18:58 15/06/2001, Arnaldo Carvalho de Melo wrote:
> >Em Fri, Jun 15, 2001 at 10:41:59AM -0700, Michael Nguyen escreveu:
> > > >>Petko Manolov writes:
> > > >> kmalloc fails to allocate more than 128KB of
> > > >> memory regardless of the flags (GFP_KERNEL/USER/ATOMIC)
> > > >>
> > > >> Any ideas?
> > >
> > > >Yes, this is the limit.
> > >
> > > Im relatively new to Linux. I would like to ask.
> > > Is this limit per kmalloc()? Can I do this multiple times?
> >
> >the limit is for a single invocation of kmalloc, yes, you can do it multiple
> >times.
>
> But if you need that much memory it would be better that you use vmalloc AFAIK.
Yup, like I suggested to Petko in a previous message :)
- Arnaldo
prev parent reply other threads:[~2001-06-15 18:49 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-06-15 17:41 RE2: kmalloc Michael Nguyen
2001-06-15 17:58 ` Arnaldo Carvalho de Melo
2001-06-15 18:26 ` Anton Altaparmakov
2001-06-15 18:46 ` Arnaldo Carvalho de Melo [this message]
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=20010615154659.A942@conectiva.com.br \
--to=acme@conectiva.com.br \
--cc=aia21@cam.ac.uk \
--cc=davem@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mnguyen@ariodata.com \
--cc=pmanolov@Lnxw.COM \
/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