On Tue, 28 Mar 2017, Zhou Chengming wrote:
> It's reported that the time of insmoding a klp.ko for one of our
> out-tree modules is too long.
Applied to for-4.12/upstream. Thanks,
--
Jiri Kosina
SUSE Labs
On Tue, 28 Mar 2017, Zhou Chengming wrote:
> It's reported that the time of insmoding a klp.ko for one of our
> out-tree modules is too long.
>
> ~ time sudo insmod klp.ko
> real 0m23.799s
> user 0m0.036s
> sys 0m21.256s
>
> Then we found the reason: our out-tree module used a lot of static
+++ Zhou Chengming [28/03/17 21:10 +0800]:
It's reported that the time of insmoding a klp.ko for one of our
out-tree modules is too long.
~ time sudo insmod klp.ko
real0m23.799s
user0m0.036s
sys 0m21.256s
Then we found the reason: our out-tree module used a lot of static local
varia
On Tue, Mar 28, 2017 at 09:10:35PM +0800, Zhou Chengming wrote:
> It's reported that the time of insmoding a klp.ko for one of our
> out-tree modules is too long.
>
> ~ time sudo insmod klp.ko
> real 0m23.799s
> user 0m0.036s
> sys 0m21.256s
>
> Then we found the reason: our out-tree module u
It's reported that the time of insmoding a klp.ko for one of our
out-tree modules is too long.
~ time sudo insmod klp.ko
real0m23.799s
user0m0.036s
sys 0m21.256s
Then we found the reason: our out-tree module used a lot of static local
variables, so klp.ko has a lot of relocation recor
5 matches
Mail list logo