From: John Levon <movement@marcelothewonderpenguin.com>
To: "Eric W. Biederman" <ebiederm@xmission.com>
Cc: Andi Kleen <ak@suse.de>, Alan Cox <alan@lxorguk.ukuu.org.uk>,
linux-kernel@vger.kernel.org
Subject: Re: Nice values for kernel modules
Date: Mon, 25 Mar 2002 08:20:30 +0000 [thread overview]
Message-ID: <20020325082029.GA41624@compsoc.man.ac.uk> (raw)
In-Reply-To: <Pine.LNX.4.33.0203161300300.1089-100000@einstein.homenet.suse.lists.linux.kernel> <E16mICa-0006mr-00@the-village.bc.nu.suse.lists.linux.kernel> <p73d6y4187b.fsf@oldwotan.suse.de> <m1pu1tum0g.fsf@frodo.biederman.org>
On Mon, Mar 25, 2002 at 12:47:27AM -0700, Eric W. Biederman wrote:
> What is wrong with using ptrace? That should already give you a hook into
> every syscall.
it's too slow, and how do you manage to follow every process ?
regards
john
--
"Way back at the beginning of time around 1970 the first man page was
handed down from on high. Every one since is an edited copy."
- John Hasler <john@dhh.gt.org>
next prev parent reply other threads:[~2002-03-25 8:21 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <Pine.LNX.4.33.0203161300300.1089-100000@einstein.homenet.suse.lists.linux.kernel>
[not found] ` <E16mICa-0006mr-00@the-village.bc.nu.suse.lists.linux.kernel>
2002-03-16 22:03 ` Andi Kleen
2002-03-25 7:47 ` Eric W. Biederman
2002-03-25 8:20 ` John Levon [this message]
[not found] <Pine.LNX.4.33.0203161126130.1090-100000@einstein.homenet.suse.lists.linux.kernel>
[not found] ` <16358.1016282075@ocs3.intra.ocs.com.au.suse.lists.linux.kernel>
[not found] ` <20020316154848.GA82190@compsoc.man.ac.uk.suse.lists.linux.kernel>
2002-03-16 16:03 ` Andi Kleen
2002-03-15 23:59 Balbir Singh
2002-03-16 9:51 ` tigran
2002-03-16 10:00 ` Keith Owens
2002-03-16 10:41 ` Paul Mackerras
2002-03-16 11:27 ` Tigran Aivazian
2002-03-16 12:34 ` Keith Owens
2002-03-16 13:04 ` Tigran Aivazian
2002-03-16 13:52 ` Christoph Hellwig
2002-03-16 17:42 ` Alan Cox
2002-03-16 15:48 ` John Levon
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=20020325082029.GA41624@compsoc.man.ac.uk \
--to=movement@marcelothewonderpenguin.com \
--cc=ak@suse.de \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=ebiederm@xmission.com \
--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
all inboxes | Powered by JetHome®