From: Christoph Rohland <cr@sap.com>
To: Mark_H_Johnson@Raytheon.com
Cc: linux-mm@kvack.org, Stanley_R_Allen-NR@Raytheon.com
Subject: Re: Locked memory questions
Date: 30 Jan 2001 10:20:57 +0100 [thread overview]
Message-ID: <m31ytmysf7.fsf@linux.local> (raw)
In-Reply-To: <OF55A69DFC.F1913EBB-ON862569DC.00556518@hou.us.ray.com>
Mark_H_Johnson@Raytheon.com writes:
> I was surprised by a reference in the latest kernel traffic
> (http://kt.linuxcare.com/kernel-traffic/latest.epl) to a VM problem with
> large locked memory regions. I read linux-mm on a daily basis, but didn't
> see this particular discussion go by.
Was this the database lockup with locked SYSV shareed memory segments?
This was not discussed a lot but fixed easily. It was a bad
implementation in shmem.c
Greetings
Christoph
--
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.eu.org/Linux-MM/
prev parent reply other threads:[~2001-01-30 9:20 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-01-22 15:54 Mark_H_Johnson
2001-01-30 9:20 ` Christoph Rohland [this message]
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=m31ytmysf7.fsf@linux.local \
--to=cr@sap.com \
--cc=Mark_H_Johnson@Raytheon.com \
--cc=Stanley_R_Allen-NR@Raytheon.com \
--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