in a followup, the only thing I can tell difference b/w the 2 runs
(under strace and inside and outside of the chroot) is that within the
chroot, after every fork() I see a SIGSTOP on the child.
anyone have any idea why this is happening?
On Thu, 2003-03-13 at 20:43, Shaya Potter wrote:
> I'm trying to play with our a homebrew version of lmbench's fork
> benchmark which exec's sh to run a "hello world" program. On normal
> 2.4.18 (UP 933mhz p3) it runs in about .2s However, within a chrooted
> environment I'm looking at 1s.
>
> Anyone knows why this runs significantly slower within a chroot?
>
> thanks,
>
> shaya
>
> -
> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at http://www.tux.org/lkml/
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
This archive was generated by hypermail 2b29 : Sat Mar 15 2003 - 22:00:37 EST