From: Miles Lane <miles@megapathdsl.net>
To: LKML <linux-kernel@vger.kernel.org>
Subject: 2.4.3-ac2 -- How do I determine if shm is being used?
Date: Sat, 07 Apr 2001 11:28:01 -0700 [thread overview]
Message-ID: <3ACF5C31.B3B0594F@megapathdsl.net> (raw)
I have mounted:
none on /var/shm type shm (rw)
tmpfs on /dev/shm type tmpfs (rw)
Yet, running "x11perf -shmput10" gives me:
X Error of failed request: BadValue (integer parameter out of range for
operation)
Major opcode of failed request: 146 (MIT-SHM)
Minor opcode of failed request: 3 (X_ShmPutImage)
Value in failed request: 0x1600001
Serial number of failed request: 35107
Current serial number in output stream: 35111
I'd like to check to make sure that shm is actually accessible
to my programs. Is there any easy way to do this?
I have already checked the values of:
/proc/sys/kernel/shmall = 2000000
/proc/sys/kernel/shmmax = 4096
/proc/sys/kernel/shmmni = 35000000
Thanks,
Miles
next reply other threads:[~2001-04-07 18:27 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-04-07 18:28 Miles Lane [this message]
2001-04-08 12:31 ` 2.4.3-ac2 -- How do I determine if shm is being used? Christoph Rohland
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=3ACF5C31.B3B0594F@megapathdsl.net \
--to=miles@megapathdsl.net \
--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