parallelizing ipfw table

[Gleb Smirnoff]

On Mon, Nov 28, 2005 at 08:32:36AM -0800, Luigi Rizzo wrote:
L> Given that you (Gleb) are putting in some new features, I would
L> suggest a variant to your tablearg thing, i.e.
L> 
L>  + a 'setvar index value' which can be put as an always-true
L>    option within a rule e.g. to store partial evaluation results.
L>    'index' could be a small integer e.g. 0-9, value a 32-bit
L>    value which is either a constant or a packet field (src-ip...)
L>    or your tablearg.
L>  + allow a 'varN' arguments everywhere you can have a rule or pipe or
L>    queue number.
L> 
L> This way you can easily implement your proposal, and a lot more.
L> One should remember that variables are not meant to be staved
L> with the packet's state (e.g. when a packet goes back and forth to
L> dummynet) but other than that i think it is a useful feature and
L> a simple one to implement.

I agree. The introduction of local variable "tablearg" is the most
unpleasant place of my patch. I will implement your proposal as soon
as we have a second think that needs to be stored during one rule
evaluation.

-- 
Totus tuus, Glebius.
GLEBIUS-RIPN GLEB-RIPE