public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Bill Davidsen <davidsen@tmr.com>
To: linux-kernel@vger.kernel.org
To: Mario Holbe <Mario.Holbe@TU-Ilmenau.DE>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Can I get 200M contiguous physical memory?
Date: Fri, 11 Mar 2005 15:39:42 -0500	[thread overview]
Message-ID: <4232020E.5050402@tmr.com> (raw)
In-Reply-To: <d0p1ag$ngk$1@sea.gmane.org>

Mario Holbe wrote:
> Jason Luo <abcd.bpmf@gmail.com> wrote:
> 
>>Now, I am writing a driver, which need 200M contiguous physical
>>memory? can do? how to do it?
> 
> 
> The ftape utils have a tool called swapout which tries to 'free'
> large chunks of memory which then can be allocated by the ftape
> module loaded subsequently.
> I don't know if this approach does also work with *such* large
> chunks like yours.

Wasn't there a problem with a process having mlocked memory in the wrong 
place and the application hanging? Or the kernel hanging? Or something. 
Can't remember.

-- 
    -bill davidsen (davidsen@tmr.com)
"The secret to procrastination is to put things off until the
  last possible moment - but no longer"  -me

  reply	other threads:[~2005-03-11 20:36 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-03-10  8:10 Can I get 200M contiguous physical memory? Jason Luo
2005-03-10  8:16 ` Chris Wedgwood
2005-03-10  8:49   ` Jason Luo
2005-03-10  8:57     ` Arjan van de Ven
2005-03-10 18:57       ` Nate Edel
2005-03-10 19:02         ` Arjan van de Ven
2005-03-10 20:28         ` linux-os
2005-03-10  9:00     ` Chris Wedgwood
2005-03-10  8:43 ` Mario Holbe
2005-03-11 20:39   ` Bill Davidsen [this message]
     [not found] <3Gr3R-5gH-23@gated-at.bofh.it>
     [not found] ` <3Grdy-5nv-3@gated-at.bofh.it>
     [not found]   ` <3GrGK-5Ff-17@gated-at.bofh.it>
     [not found]     ` <3GrQf-5Vr-27@gated-at.bofh.it>
2005-03-11  2:20       ` Robert Hancock

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=4232020E.5050402@tmr.com \
    --to=davidsen@tmr.com \
    --cc=linux-kernel@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