From: Steven Brown <swbrown@ucsd.edu>
To: linux-kernel@vger.kernel.org
Subject: /proc/(pid)/mem status and future, or alternatives?
Date: Fri, 27 Oct 2000 03:46:09 -0700 [thread overview]
Message-ID: <00102703460900.02088@depraved.org> (raw)
Hi, I had noticed that the mmapping facilities of /proc/(pid)/mem have been
removed in recent devel kernels as well as in the 2.4 test series. I assume
that since it is missing in the test series, that it is to be missing in
2.4.0 final as well. I poked around on the list archives and found mention
of its demise, but couldn't find any indication as to if it was a permanent
removal or if it was just temporary while issues were sorted out, or to
alternatives to use for the same functionality. Is there another way to get
access to another process's memory space in bulk? I need to do a full search
on an arbitrary process's memory space. I've been using
ptrace(PTRACE_PEEKDATA, ..) in the absense of the ability to mmap the
process's memory but doing so takes a few million system calls per search
which is prohibitively expensive.
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
Please read the FAQ at http://www.tux.org/lkml/
reply other threads:[~2000-10-27 10:46 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=00102703460900.02088@depraved.org \
--to=swbrown@ucsd.edu \
--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