netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: David Miller <davem@davemloft.net>
To: shemminger@vyatta.com
Cc: yoshfuji@linux-ipv6.org, herbert@gondor.apana.org.au,
	netdev@vger.kernel.org
Subject: Re: [RFC] gre: propagate ipv6 transport class
Date: Thu, 08 Jul 2010 21:36:45 -0700 (PDT)	[thread overview]
Message-ID: <20100708.213645.183036637.davem@davemloft.net> (raw)
In-Reply-To: <20100706105821.7b0e2538@nehalam>

From: Stephen Hemminger <shemminger@vyatta.com>
Date: Tue, 6 Jul 2010 10:58:21 -0700

> This patch makes IPV6 over IPv4 GRE tunnel propagate the transport
> class field from the underlying IPV6 header to the IPV4 Type Of Service
> field. Without the patch, all IPV6 packets in tunnel look the same to QoS.
> 
> This assumes that IPV6 transport class is exactly the same
> as IPv4 TOS. Not sure if that is always the case?  Maybe need
> to mask off some bits.
> 
> The mask and shift to get tclass is copied from ipv6/datagram.c
> 
> Signed-off-by: Stephen Hemminger <shemminger@vyatta.com>

Looks good, but we should use ipv6_get_dsfield() just like
ipgre_ecn_encapsulate() does.

Note that this also influences the route since this 'tos' feeds
into the flowi lookup key.  We should make sure that this is OK
too.

Anyways, I've committed the following to net-next-2.6, thanks!

--------------------
gre: propagate ipv6 transport class

This patch makes IPV6 over IPv4 GRE tunnel propagate the transport
class field from the underlying IPV6 header to the IPV4 Type Of Service
field. Without the patch, all IPV6 packets in tunnel look the same to QoS.

This assumes that IPV6 transport class is exactly the same
as IPv4 TOS. Not sure if that is always the case?  Maybe need
to mask off some bits.

The mask and shift to get tclass is copied from ipv6/datagram.c

Signed-off-by: Stephen Hemminger <shemminger@vyatta.com>
Signed-off-by: David S. Miller <davem@davemloft.net>
---
 net/ipv4/ip_gre.c |    2 ++
 1 files changed, 2 insertions(+), 0 deletions(-)

diff --git a/net/ipv4/ip_gre.c b/net/ipv4/ip_gre.c
index 749e548..945b20a 100644
--- a/net/ipv4/ip_gre.c
+++ b/net/ipv4/ip_gre.c
@@ -731,6 +731,8 @@ static netdev_tx_t ipgre_tunnel_xmit(struct sk_buff *skb, struct net_device *dev
 		tos = 0;
 		if (skb->protocol == htons(ETH_P_IP))
 			tos = old_iph->tos;
+		else if (skb->protocol == htons(ETH_P_IPV6))
+			tos = ipv6_get_dsfield((struct ipv6hdr *)old_iph);
 	}
 
 	{
-- 
1.7.1.1




      reply	other threads:[~2010-07-09  4:36 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-07-06 17:58 [RFC] gre: propagate ipv6 transport class Stephen Hemminger
2010-07-09  4:36 ` David Miller [this message]

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=20100708.213645.183036637.davem@davemloft.net \
    --to=davem@davemloft.net \
    --cc=herbert@gondor.apana.org.au \
    --cc=netdev@vger.kernel.org \
    --cc=shemminger@vyatta.com \
    --cc=yoshfuji@linux-ipv6.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).