From: ebiederm@xmission.com (Eric W. Biederman)
To: "Amit S. Jain" <amitjain@tifr.res.in>
Cc: linux-mm@kvack.org
Subject: Re: Allocation of kernel memory >128K
Date: 11 Dec 2001 03:41:01 -0700 [thread overview]
Message-ID: <m1k7vuujia.fsf@frodo.biederman.org> (raw)
In-Reply-To: <Pine.LNX.4.21.0112111531110.5038-100000@mailhost.tifr.res.in>
"Amit S. Jain" <amitjain@tifr.res.in> writes:
> I have been working on a module in which I copy large amount of data fromn
> the user to the kernel area.To do so I allocate using either kmaaloc or
> vmalloc or get_free_pages()large amount of memory(in the range of
> MBytes) in the kernel space.However this attempt is not successful.One ofmy
> colleagues informed me that in the kernel space it is safe not to allocate
> large amount of memory at one time,should be kept upto 30K...is he
> right....could you throw more light on this issue.
large amounts of memory are o.k.
large amounts of continuous memory is generally a bad thing.
Allocating everything with multiple calls to get_free_page() should
get the job done.
Eric
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org. For more info on Linux MM,
see: http://www.linux-mm.org/
next prev parent reply other threads:[~2001-12-11 10:41 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-12-11 10:06 Allocation of kernel memory >128K Amit S. Jain
2001-12-11 10:41 ` Eric W. Biederman [this message]
2001-12-12 7:40 ` Amit S. Jain
2001-12-20 3:56 ` Vladimir Dergachev
2001-12-27 11:08 ` Amit S. Jain
2002-01-03 22:59 ` Ravi K
-- strict thread matches above, loose matches on Subject: below --
2001-12-11 15:27 Mark_H_Johnson
2001-12-11 18:13 ` Benjamin LaHaise
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=m1k7vuujia.fsf@frodo.biederman.org \
--to=ebiederm@xmission.com \
--cc=amitjain@tifr.res.in \
--cc=linux-mm@kvack.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.