that multi-threading (Re: funny `dash` build, `sed` + BRE (Re: shell and glibc))

[Oleg Verych <olecom@xxxxxxxxxxxxxx>]

Forgot one thing.

> == Let strange quark decay ==
> 
> $time sed -n '/:Version: /s`.*/\(.*\):Version: \([^:]*:\)*`\1_`p' <sed.input >here2
> 
> real    0m0.284s
> user    0m0.268s
> sys     0m0.020s
> $diff -u here here2 | head
> $
> 
> So, nearly one order of magnitude?

$time sed -n '/:Version: /s`.*/\(.*\):Version: \([^:]*:\)*`\1_`p' <sed.input >here2

real    0m0.283s
user    0m0.268s
sys     0m0.012s
$
$time sed -n '/:Version: /s`.*/``p' <sed.input | sed 's`\(.*\):Version: \([^:]*:\)*`\1_`' >here3

real    0m0.142s
user    0m0.188s
sys     0m0.012s
$
$time sed -n '/:Version: /s`.*/``p' <sed.input | sed 's`\(.*\):Version: \([^:]*:\)*`\1_`' >here3

real    0m0.142s
user    0m0.184s
sys     0m0.008s
$
$diff -u here3 here2
$

Linuxthreads in past TODO or yet TO DO NPTL for faster ERE in glibc?

I think, making processes in kernel light, new scheduler, splice(), etc,
etc, is better way, rather than inventing userspace-multi-tasking.

I wonder, who needs it anyway, except big closed enterprise...
____
--
To unsubscribe from this list: send the line "unsubscribe dash" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html