linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: "Amit S. Jain" <amitjain@tifr.res.in>
To: linux-mm@kvack.org
Subject: Allocation of kernel memory >128K
Date: Thu, 27 Dec 2001 16:38:08 +0530 (IST)	[thread overview]
Message-ID: <Pine.LNX.4.21.0112271634010.29530-100000@mailhost.tifr.res.in> (raw)
In-Reply-To: <Pine.LNX.4.21.0112111531110.5038-100000@mailhost.tifr.res.in>

Hello everyone,
		I hope u can clear this doubt.This question is a
continuation of the question below which i had posted on this site

On Tue, 11 Dec 2001, Amit S. Jain wrote:

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

  I WANT TO KNOW WHAT AMOUNT OF MEMORY ALLOCATION WILL BE SAFE.i.e. even
if i alloc 30K at a time,will I always get a contiguous memory for that
purpose.??
	Is there a set limit in Linux for the amount of memory we obtain
will always be contiguous or always available??
 
 
Thanking you,
 Amit Jain
 

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

  parent reply	other threads:[~2001-12-27 11:08 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-12-11 10:06 Amit S. Jain
2001-12-11 10:41 ` Eric W. Biederman
2001-12-12  7:40   ` Amit S. Jain
2001-12-20  3:56     ` Vladimir Dergachev
2001-12-27 11:08 ` Amit S. Jain [this message]
2002-01-03 22:59   ` Ravi K
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=Pine.LNX.4.21.0112271634010.29530-100000@mailhost.tifr.res.in \
    --to=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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox