Searched refs:flowsets (Results 1 – 2 of 2) sorted by relevance
| /freebsd/sys/netpfil/ipfw/test/ |
| H A D | main.c | 36 int flowsets; /* number of flowsets */ member
325 DX(3, "--- pass %d flows %d flowsets %d", pass, c->flows, c->flowsets); in parse_flowsets()
377 if (c->fs == NULL || c->flowsets <= n_fs) { in parse_flowsets()
396 c->flowsets = n_fs; in parse_flowsets()
402 DX(1,"%d flows on %d flowsets", c->flows, c->flowsets); in parse_flowsets()
405 DX(1,"%d flows on %d flowsets max_y %d", c->flows, c->flowsets, c->max_y); in parse_flowsets()
407 for (i=0; i < c->flowsets; i++) { in parse_flowsets()
448 c->flowsets = 1; in init()
498 DX(3, "setting flowsets to %d", c->flowsets); in init()
512 if (c->flowsets <= 0) in init()
[all …]
|
| /freebsd/sys/netpfil/ipfw/ |
| H A D | dummynet.txt | 52 association of flowsets and schedulers is configurable e.g.
149 CREATE: configuration command. If there are flowsets that
173 schedulers and flowsets.
176 Looked up only on manual configurations, where flowsets
181 - fshash[x]: contains all flowsets.
396 scheduler number. If some are found, flowsets became of the type of this
433 Finally, flowsets in the unlinked flowset list are write in the buffer, and
498 scheduler with the same number is inserted will use these flowsets.
501 So flowsets will remain in memory and linked with a scheduler that no
|