Searched refs:flowsets (Results 1 – 2 of 2) sorted by relevance
| /f-stack/freebsd/netpfil/ipfw/test/ |
| H A D | main.c | 37 int flowsets; /* number of flowsets */ member
378 if (c->fs == NULL || c->flowsets <= n_fs) { in parse_flowsets()
397 c->flowsets = n_fs; in parse_flowsets()
403 DX(1,"%d flows on %d flowsets", c->flows, c->flowsets); in parse_flowsets()
408 for (i=0; i < c->flowsets; i++) { in parse_flowsets()
449 c->flowsets = 1; in init()
499 DX(3, "setting flowsets to %d", c->flowsets); in init()
513 if (c->flowsets <= 0) in init()
514 c->flowsets = 1; in init()
551 c->fs = calloc(c->flowsets, sizeof(struct dn_fsk)); in init()
[all …]
|
| /f-stack/freebsd/netpfil/ipfw/ |
| H A D | dummynet.txt | 53 association of flowsets and schedulers is configurable e.g.
150 CREATE: configuration command. If there are flowsets that
174 schedulers and flowsets.
177 Looked up only on manual configurations, where flowsets
182 - fshash[x]: contains all flowsets.
397 scheduler number. If some are found, flowsets became of the type of this
434 Finally, flowsets in the unlinked flowset list are write in the buffer, and
499 scheduler with the same number is inserted will use these flowsets.
502 So flowsets will remain in memory and linked with a scheduler that no
|