nfmark is being used in various subsystems and has become
the defacto mark field for all kinds of packets. Therefore
it makes sense to rename it to `mark' and remove the
dependency on CONFIG_NETFILTER.
Signed-off-by: Thomas Graf [EMAIL PROTECTED]
Index: net-2.6.20/include/linux/skbuff.h
Another thought: sometimes a single mark makes rulesets inconvenient.
What about several independent marks on a packet?
--
Meelis Roos [EMAIL PROTECTED]
-
To unsubscribe from this list: send the line unsubscribe netdev in
the body of a message to [EMAIL PROTECTED]
More majordomo info at
* Meelis Roos [EMAIL PROTECTED] 2006-11-09 14:32
Another thought: sometimes a single mark makes rulesets inconvenient.
What about several independent marks on a packet?
The mark is already a bitfield, you may dividide it into separate
marks with the exception of routes which do not yet support
The mark is already a bitfield, you may dividide it into separate
marks with the exception of routes which do not yet support a
mask.
Just checked, now that we have --and-mask and --or-mask, this is much
better than before.
The bitmask is OK when up to 32 marks are needed (like, for
From: Thomas Graf [EMAIL PROTECTED]
Date: Thu, 09 Nov 2006 12:27:36 +0100
nfmark is being used in various subsystems and has become
the defacto mark field for all kinds of packets. Therefore
it makes sense to rename it to `mark' and remove the
dependency on CONFIG_NETFILTER.
Signed-off-by:
