| To: | Alexey <kuznet@xxxxxxxxxxxxx> |
|---|---|
| Subject: | Re: Fw: issues with SO_PRIORITY and IP_TOS |
| From: | Jamal Hadi Salim <hadi@xxxxxxxx> |
| Date: | 04 Nov 2003 11:04:26 -0500 |
| Cc: | "David S. Miller" <davem@xxxxxxxxxx>, jmorris@xxxxxxxxxx, cfriesen@xxxxxxxxxxxxxxxxxx, netdev@xxxxxxxxxxx |
| In-reply-to: | <200311041233.PAA15518@yakov.inr.ac.ru> |
| Organization: | Znyx Networks |
| References: | <200311041233.PAA15518@yakov.inr.ac.ru> |
| Reply-to: | hadi@xxxxxxxx |
| Sender: | netdev-bounce@xxxxxxxxxxx |
Hi, I agree with Alexey in regards to DSCP should be done by classifiers. Current mode of operation is: Whatever DSCP value you set will be reset by the network/box manager depending on some criteria they set. Applications running as root or sudo can of course open a netlink connection and set these values via a classifier. Actually one important thing easy to miss is that the IEEE priorities are reverse to what the IETF priorities are (who would have thunk, eh?). I havent looked at the VLAN code however blindly using the sk/skb->priority is _bad_ given that sk/skb->priority is based on IETF semantics. I bet you the Linux vlan code doesnt know this. cheers, jamal |
| <Prev in Thread] | Current Thread | [Next in Thread> |
|---|---|---|
| ||
| Previous by Date: | Fwd: tcp checksumming, Russell King |
|---|---|
| Next by Date: | Re: Fw: issues with SO_PRIORITY and IP_TOS, Chris Friesen |
| Previous by Thread: | Re: Fw: issues with SO_PRIORITY and IP_TOS, kuznet |
| Next by Thread: | Re: Fw: issues with SO_PRIORITY and IP_TOS, Chris Friesen |
| Indexes: | [Date] [Thread] [Top] [All Lists] |