Re: [PATCH 2/6] test_bpf: allow tests to specify an skb fragment.
From: Daniel Borkmann
Date: Mon Aug 03 2015 - 13:37:45 EST
On 08/03/2015 06:38 PM, Nicolas Schichan wrote:
On 08/03/2015 05:29 PM, Daniel Borkmann wrote:
On 08/03/2015 04:02 PM, Nicolas Schichan wrote:
We now have 286 tests, which is awesome!
Perhaps, we need to start thinking of a better test description method
soonish as the test_bpf.ko module grew to ~1.6M, i.e. whenever we add
to struct bpf_test, it adds memory overhead upon all test cases.
Indeed, test_bpf.ko is turning quite large (1.4M when compiled for ARM).
It looks like gzip is able to do wonders on the module though as I end up with
a 94.7K test_bpf.ko.gz file and if the modutils are compiled with
--enable-zlib, it will be gunziped automatically before being loaded to the
kernel.
I think it just contains a lot of zero blocks, which then compress nicely.
I think that marking tests[] array as __initdata will help with the runtime
memory use if someone forgets to rmmod the test_bpf module after a completely
successful run.
Can be done, too, yep. Do you want to send a patch? ;)
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/