From: Mark_H_Johnson@Raytheon.com
To: anand kumar <a_santha@rediffmail.com>
Cc: kernelnewbies@nl.linux.org, linux-mm@kvack.org
Subject: Re: Memory allocation problem
Date: Thu, 1 May 2003 08:20:56 -0500 [thread overview]
Message-ID: <OF15CF6B9C.D9504382-ON86256D19.00484B29@hou.us.ray.com> (raw)
>The kernel version we are using is 2.4.18 (Redhat 8.0) and the total
>amount of memory available in the box is 128MB
>Is there any other mechanism to allocate large amount of physically
>contiguous memory blocks during normal run time of the driver? Is this
>being addressed in later kernels.
I regularly use a patch (bigphysarea) recommended by Dolphin for use with
their SCI cards. The copy I use is from a relatively old kernel (2.4.4)
which applies with a few warnings but is otherwise OK. I did a quick search
with Google for
bigphysarea linux 2.4.18
and found
http://frmb.home.cern.ch/frmb/download/bigphysarea-2.4.18.patch
or a more readable page at
http://frmb.home.cern.ch/frmb/linux.html
which appears to be a version updated for 2.4.18. I believe the original
patch is maintained at
http://www.uni-paderborn.de/fachbereich/AG/heiss/linux/bigphysarea.html
There are apparently several drivers that already use this interface, but
it does require a patched kernel.
I am not aware of any effort to merge this into the main line kernel
(though I would certainly appreciate that).
--Mark H Johnson
<mailto:Mark_H_Johnson@raytheon.com>
--
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/ .
Don't email: <a href=mailto:"aart@kvack.org"> aart@kvack.org </a>
next reply other threads:[~2003-05-01 13:20 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-05-01 13:20 Mark_H_Johnson [this message]
-- strict thread matches above, loose matches on Subject: below --
2003-04-30 22:14 anand kumar
2003-04-30 22:28 ` Greg KH
2003-04-30 22:29 ` Christoph Hellwig
2003-04-30 22:36 ` Dave Hansen
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=OF15CF6B9C.D9504382-ON86256D19.00484B29@hou.us.ray.com \
--to=mark_h_johnson@raytheon.com \
--cc=a_santha@rediffmail.com \
--cc=kernelnewbies@nl.linux.org \
--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