On Sat, Sep 4, 2010 at 12:58 AM, Akshat Kumar
wrote:
> Is ratrace usable on native Plan 9 (I understand it's in use on 9vx
> thus far)? I don't see a /proc/n/syscall file for any of my processes;
> is there some kernel patch for this?
One could take the modified version of my syscall tracing code
On Sat Sep 4 03:59:16 EDT 2010, aku...@mail.nanosouffle.net wrote:
> Is ratrace usable on native Plan 9 (I understand it's in use on 9vx
> thus far)? I don't see a /proc/n/syscall file for any of my processes;
> is there some kernel patch for this?
acid is perfectly capabible of doing this.
see t
Is ratrace usable on native Plan 9 (I understand it's in use on 9vx
thus far)? I don't see a /proc/n/syscall file for any of my processes;
is there some kernel patch for this?
Thanks,
ak
On Fri, Sep 3, 2010 at 10:14 PM, ron minnich wrote:
> Glibc /bin/date on Linux runs around 140 system calls.
Glibc /bin/date on Linux runs around 140 system calls. A quick pass
with ratrace shows that plan 9 /bin/date has 10.
The conclusion is clear: plan 9 date has way too much overhead. It's
1/14 the number of system calls of Glibc; why's it so big?
A quick pass on getpid() fixes the problem:
#includ