From: Mark_H_Johnson@raytheon.com
To: root@chaos.analogic.com
Cc: Dave Hansen <haveblue@us.ibm.com>,
linux-kernel <linux-kernel@vger.kernel.org>,
linux-mm <linux-mm@kvack.org>,
Timothy Miller <miller@techsource.com>,
owner-linux-mm@kvack.org, Alok Mooley <rangdi@yahoo.com>
Subject: Re: Active Memory Defragmentation: Our implementation & problems
Date: Wed, 4 Feb 2004 14:12:17 -0600 [thread overview]
Message-ID: <OFE7103176.29D4436D-ON86256E30.006E41D8@raytheon.com> (raw)
Richard B. Johnson wrote:
>Eventually you
>get to the fact that even contiguous physical RAM doesn't
>have to be contiguous and, in fact, with modern controllers
>it's quite unlikely that it is. It's a sack of bits that
>are uniquely addressable.
Yes and no. We are using a shared memory interface on a cluster that allows
us to map up to 512 Mbytes of memory from another machine. There are 16k
address translation table (ATT) entries in the card, so we're allocating
32K chunks of memory per ATT. We are using the bigphysarea patch for the
driver (in 2.4 kernels) only because the driver can't reliably get the
chunks of RAM it is asking for. We can continue to operate the way we've
been doing or get a mechanism to defragment physical RAM so the driver can
continue to work a week after we rebooted the machine.
--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:[~2004-02-04 20:12 UTC|newest]
Thread overview: 34+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-02-04 20:12 Mark_H_Johnson [this message]
-- strict thread matches above, loose matches on Subject: below --
2004-02-03 4:46 Alok Mooley
2004-02-03 21:26 ` Dave Hansen
2004-02-03 22:26 ` Martin J. Bligh
2004-02-04 5:09 ` Alok Mooley
2004-02-04 5:24 ` Mike Fedyk
2004-02-04 5:54 ` Dave Hansen
2004-02-04 6:05 ` Martin J. Bligh
2004-02-04 6:22 ` Dave Hansen
2004-02-04 6:29 ` Martin J. Bligh
2004-02-04 6:40 ` Dave Hansen
2004-02-04 7:17 ` Martin J. Bligh
2004-02-04 8:30 ` Andrew Morton
2004-02-04 6:57 ` IWAMOTO Toshihiro
2004-02-04 7:10 ` Dave Hansen
2004-02-04 7:50 ` IWAMOTO Toshihiro
2004-02-04 10:33 ` Hirokazu Takahashi
2004-02-04 18:33 ` Alok Mooley
2004-02-04 18:46 ` Dave Hansen
2004-02-04 18:54 ` Alok Mooley
2004-02-04 19:07 ` Richard B. Johnson
2004-02-04 19:18 ` Alok Mooley
2004-02-04 19:33 ` Richard B. Johnson
2004-02-05 5:07 ` Alok Mooley
2004-02-05 19:03 ` Pavel Machek
2004-02-04 19:35 ` Dave McCracken
2004-02-04 21:59 ` Timothy Miller
2004-02-04 23:24 ` Dave Hansen
2004-02-05 16:32 ` Dave McCracken
2004-02-04 19:37 ` Timothy Miller
2004-02-04 19:43 ` Dave Hansen
2004-02-04 19:59 ` Richard B. Johnson
2004-02-04 19:56 ` Dave Hansen
2004-02-05 5:19 ` Alok Mooley
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=OFE7103176.29D4436D-ON86256E30.006E41D8@raytheon.com \
--to=mark_h_johnson@raytheon.com \
--cc=haveblue@us.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=miller@techsource.com \
--cc=owner-linux-mm@kvack.org \
--cc=rangdi@yahoo.com \
--cc=root@chaos.analogic.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