* setsockopt: SO_PRIORITY and IP_TOS
@ 2005-03-04 1:02 Ben Greear
0 siblings, 0 replies; only message in thread
From: Ben Greear @ 2005-03-04 1:02 UTC (permalink / raw)
To: 'netdev@oss.sgi.com'
With regard to 2.6.11-rc4 (and probably others).
I just noticed something that struck me as a bit strange.
Might be per design though...
If you set the IP_TOS and then the SO_PRIORITY for a socket,
the TOS is what you set it to, and so is the priority.
However, if you set the PRIORITY (to 55, in my case)
and then set the IP_TOS (to 3, in my case), then the priority
will be re-set to 0.
My opinion is that setting the IP_TOS should not affect the priority,
especially if it has already been specifically set on that socket.
Thanks,
Ben
--
Ben Greear <greearb@candelatech.com>
Candela Technologies Inc http://www.candelatech.com
^ permalink raw reply [flat|nested] only message in thread
only message in thread, other threads:[~2005-03-04 1:02 UTC | newest]
Thread overview: (only message) (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2005-03-04 1:02 setsockopt: SO_PRIORITY and IP_TOS Ben Greear
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).