From: Rick Jones <rick.jones2-VXdhtT5mjnY@public.gmane.org>
To: netdev-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Cc: dave.taht-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org,
amirv-LDSdmyG8hGV8YrgS2mwiifqBs+8SCbDb@public.gmane.org,
mkt.manpages-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org,
linux-man-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Subject: is SO_PRIORITY still supposed to affect the TOS field?
Date: Thu, 25 Aug 2011 14:52:05 -0700 [thread overview]
Message-ID: <4E56C405.3030407@hp.com> (raw)
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-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
reply other threads:[~2011-08-25 21:52 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4E56C405.3030407@hp.com \
--to=rick.jones2-vxdhtt5mjny@public.gmane.org \
--cc=amirv-LDSdmyG8hGV8YrgS2mwiifqBs+8SCbDb@public.gmane.org \
--cc=dave.taht-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org \
--cc=linux-man-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=mkt.manpages-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org \
--cc=netdev-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
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).