1 Jul 2011 15:34
2 Jul 2011 12:55
r4706 - trunk/PF_RING/userland/lib
<svn-commit <at> ntop.org>
2011-07-02 10:55:31 GMT
2011-07-02 10:55:31 GMT
Author: cardigliano Date: 2011-07-02 12:55:31 +0200 (Sat, 02 Jul 2011) New Revision: 4706 Modified: trunk/PF_RING/userland/lib/pfring.c trunk/PF_RING/userland/lib/pfring_mod_dna.c trunk/PF_RING/userland/lib/pfring_mod_dna.h Log: removed vdna support (use dna + passthrough on VMs)
5 Jul 2011 11:15
5 Jul 2011 23:27
6 Jul 2011 00:14
Help needed in understanding the relation between cluster num and min_num_slots
Adayadil Thomas <adayadil.thomas <at> gmail.com>
2011-07-05 22:14:40 GMT
2011-07-05 22:14:40 GMT
Hello and greetings! Is there a reason for having the CLUSTER_LEN set to 8 in pf_ring kernel module? And how is it related to the module parameter min_num_slots and caplen? By default, the min_num_slots will be 4096. If I change that to 16384, and try adding 8 sockets to a cluster I get a kernel panic. I am trying to understand the relation between the parameters here. In all cases when the clusternum * caplen * min_num_slots is greater than a certain number, the vmalloc_user in the kernel gives issues and a panic happens. I don't know the reason, is there a limit to how much vmalloc_user() can allocate? Please note that this is for linux kernel 2.6.18.194. Thanks for the help.
6 Jul 2011 13:50
Re: Help needed in understanding the relation between cluster num and min_num_slots
Luca Deri <deri <at> ntop.org>
2011-07-06 11:50:28 GMT
2011-07-06 11:50:28 GMT
Thomas the cluster size set to 8 is to set a reasonable upper limit. What would you expect as limit? Also, why do you want to increase the number of slots? It has been configurable as people might experiment with it, but in general enlarging the number of slots you have a larger buffer (and thus more time to handle traffic peaks) but at the same time you increase cache misses and thus performance. if the vmalloc cannot find memory, it can report the error. So I don't see major benefits changing defaults. Luca On Jul 6, 2011, at 12:14 AM, Adayadil Thomas wrote: > Hello and greetings! > > Is there a reason for having the CLUSTER_LEN set to 8 in pf_ring > kernel module? And how is it related to the module parameter > min_num_slots and caplen? > By default, the min_num_slots will be 4096. If I change that to 16384, > and try adding 8 sockets to a cluster I get a kernel panic. I am > trying to understand the relation between the parameters here. > > In all cases when the clusternum * caplen * min_num_slots is greater > than a certain number, the vmalloc_user in the kernel gives issues and > a panic happens. I don't know the reason, is there a limit to how much > vmalloc_user() can allocate? > > Please note that this is for linux kernel 2.6.18.194. > > Thanks for the help. > _______________________________________________(Continue reading)
6 Jul 2011 14:33
r4709 - in trunk/PF_RING/userland: examples lib
<svn-commit <at> ntop.org>
2011-07-06 12:33:53 GMT
2011-07-06 12:33:53 GMT
Author: cardigliano Date: 2011-07-06 14:33:53 +0200 (Wed, 06 Jul 2011) New Revision: 4709 Modified: trunk/PF_RING/userland/examples/Makefile trunk/PF_RING/userland/examples/pfcount.c trunk/PF_RING/userland/lib/pfring_mod_dag.c trunk/PF_RING/userland/lib/pfring_mod_dag.h Log: DAG support update
7 Jul 2011 10:03
7 Jul 2011 22:25
r4711 - trunk/PF_RING/userland/lib
<svn-commit <at> ntop.org>
2011-07-07 20:25:57 GMT
2011-07-07 20:25:57 GMT
Author: cardigliano Date: 2011-07-07 22:25:57 +0200 (Thu, 07 Jul 2011) New Revision: 4711 Modified: trunk/PF_RING/userland/lib/pfring.c trunk/PF_RING/userland/lib/pfring_mod_dag.c trunk/PF_RING/userland/lib/pfring_mod_dag.h Log: dag module fix
RSS Feed