is SO_PRIORITY still supposed to affect the TOS field?

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Amir Vadai recently sent me some patches for netperf to implement setting SO_PRIORITY. I made changes to netperf based on those patches, (now in top of trunk on netperf.org) and between some emails with me, him and Dave Taht and some quick messing around while watching tcpdump, I'm wondering if this:

      SO_PRIORITY
              Set the protocol-defined priority for all packets to be sent  on
              this  socket.   Linux  uses  this  value to order the networking
              queues: packets with a higher priority may  be  processed  first
              depending  on  the  selected  device  queueing  discipline.  For
              ip(7), this also sets the IP  type-of-service  (TOS)  field  for
              outgoing  packets.   Setting a priority outside the range 0 to 6
              requires the CAP_NET_ADMIN capability.

from the socket(7) manpage is still accurate because even setting a number of different values for SO_PRIORITY I didn't see the TOS field as anything other than 0 in tcpdump output (confirming something Dave Taht saw).

happy benchmarking,

rick jones
--
To unsubscribe from this list: send the line "unsubscribe linux-man" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html


[Index of Archives]     [Kernel Documentation]     [Netdev]     [Linux Ethernet Bridging]     [Linux Wireless]     [Kernel Newbies]     [Security]     [Linux for Hams]     [Netfilter]     [Bugtraq]     [Yosemite News]     [MIPS Linux]     [ARM Linux]     [Linux RAID]     [Linux Admin]     [Samba]

  Powered by Linux