From: Albert Cahalan <albert@users.sf.net>
To: linux-kernel mailing list <linux-kernel@vger.kernel.org>
Subject: SysV shm device number
Date: 29 Jan 2004 10:05:22 -0500 [thread overview]
Message-ID: <1075388721.15653.124.camel@cube> (raw)
I'd like to reliably identify SysV shared memory
in the /proc/*/maps files. On one system, the entries
look like this:
40014000-40015000 r--s 00000000 00:04 0 /SYSV00000000 (deleted)
40015000-40016000 rw-s 00000000 00:04 32769 /SYSV000000ff (deleted)
On my system, they look like this:
30016000-30017000 r--s 00000000 00:06 870318096 /SYSV00000000\040(deleted)
30017000-30018000 rw-s 00000000 00:06 870350865 /SYSV000000ff\040(deleted)
So the key number is in the name, and the shmid
number is the inode number. The device major number
is 0, and the device minor number is 4 or 6.
Other than by creating my own SysV shared memory,
is there a way to tell what the minor number
should be?
next reply other threads:[~2004-01-29 17:23 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-01-29 15:05 Albert Cahalan [this message]
2004-01-29 19:55 ` SysV shm device number Hugh Dickins
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=1075388721.15653.124.camel@cube \
--to=albert@users.sf.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.