-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256 Hello Christine,
I googled a bit and some doc[1] says that TC_PRIO_INTERACTIVE maps to value 6, whatever that is. Assuming that value of 6 is the same as the "priority value", Corosync traffic should go into band 0, because TOS values of 0x10 and 0x14 have "priority value" 6, too. The page[2] on lartc.org says that, too. That means that at least when pfifo_fast is used, there's no need for iptables rules or tc filters to prioritize Corosync traffic manually. [1] http://linux-tc-notes.sourceforge.net/tc/doc/priority.txt [2] http://lartc.org/howto/lartc.qdisc.classless.html#AEN658 - -- Mit freundlichen Grüßen/Kind Regards, Noel Kuntze GPG Key ID: 0x63EC6658 Fingerprint: 23CA BB60 2146 05E7 7278 6592 3839 298F 63EC 6658 -----BEGIN PGP SIGNATURE----- Version: GnuPG v2 iQIcBAEBCAAGBQJV9t2yAAoJEDg5KY9j7GZYA88P/3RVecICvk8PPSkP00SzUwB4 Rz1UCPyrT68y0ndvxWo9XL4aVBjKskmFHCD6db74hn6LOwa91l0lgV/ii6CZWHge 2Bvp3TVM18BzWN/iy+4AbAKHQ8wayLH/c1P1lRy8BYDCVvLK8/hT36A8TOPYhCFa cXQcD1cGfAbfTlFTc1UjuJRjniPA8SOwHtbRNfSdJw6PznYX7smGy3tfcu7bpGRe 6Q62eaayZn1P3tZb3yc1Jt/J237pf9GMBCqLu6SRg0+yKJpgyhfSBgMtg7rCrPP3 ax6ta6ypXgIucCgp68vo78k1hcXwIDmUbvkuaR+su0GTulFIhl6qh74l+3UDFISH hICNa0TdznFX0JHy3hsko+W97zC5ywMNCm/RTiy6DckHnshZyuLS5G1gh50AGhgc tGMn1K06fIqmpq+MogRvZeszNOqm43qTBGGD1oXYOIcJnBbIYuUevLs5xoKWkwS8 afqvIWjFeNIKkEDjla8h9RblpzLAZ8uR68m2jYrev81Bb14DqUnVb2m3DcbqwYIS x7wtoY4Mxj3c4joH+xiJ/Hk2JXf+S2JqoDFwcyLoh3gfAle7YAhx9cl93xCjJgf5 7CsTrojhRyLgOcvFnMpCB6r6guNVGqFN4kUvgP7eMWxBLpEE53CS4V44YS1QJkGR 6z+6w1a02L2UAgVI16Oj =Q8Dc -----END PGP SIGNATURE----- _______________________________________________ Users mailing list: Users@clusterlabs.org http://clusterlabs.org/mailman/listinfo/users Project Home: http://www.clusterlabs.org Getting started: http://www.clusterlabs.org/doc/Cluster_from_Scratch.pdf Bugs: http://bugs.clusterlabs.org