Re: ip_flow and ipf_tos

2002-04-30 Thread Terry Lambert
mark tinguely wrote: > > Right now, ip_tos (and ipf_tos) is an 8 bit value, of which only > > the first 6 bits are used in the hash, while the hash value pass > > itself is a 32 bit value (in most cases: it's "unsigned"). I'd > > like to push the value into the same space as the src.s_addr >

Re: ip_flow and ipf_tos

2002-04-30 Thread mark tinguely
> Right now, ip_tos (and ipf_tos) is an 8 bit value, of which only > the first 6 bits are used in the hash, while the hash value pass > itself is a 32 bit value (in most cases: it's "unsigned"). I'd > like to push the value into the same space as the src.s_addr > feedback, which would have

ip_flow and ipf_tos

2002-04-28 Thread Terry Lambert
It seems to me that it would be useful to break out the ip_tos field in the ipflow_lookup() function, just like in the ipflow_hash() function, and make it an unsigned long (the packing of the structure makes it a 32 bit value (or 64 bit, on Alpha) anyway. This also means calling the mtod() (which