netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Patrick McHardy <kaber@trash.net>
To: Arnd Bergmann <arnd@arndb.de>
Cc: Eric Dumazet <eric.dumazet@gmail.com>,
	linux-kernel@vger.kernel.org, netdev@vger.kernel.org,
	David Miller <davem@davemloft.net>,
	Stephen Hemminger <shemminger@vyatta.com>,
	Herbert Xu <herbert@gondor.apana.org.au>,
	Patrick Mullaney <pmullaney@novell.com>,
	"Eric W. Biederman" <ebiederm@xmission.com>,
	Edge Virtual Bridging <evb@yahoogroups.com>,
	Anna Fischer <anna.fischer@hp.com>,
	bridge@lists.linux-foundation.org,
	virtualization@lists.linux-foundation.org,
	Jens Osterkamp <jens@linux.vnet.ibm.com>,
	Gerhard Stenzel <gerhard.stenzel@de.ibm.com>,
	Mark Smith <lk-netdev@lk-netdev.nosense.org>
Subject: Re: [PATCH 1/4] veth: move loopback logic to common location
Date: Tue, 24 Nov 2009 11:17:11 +0100	[thread overview]
Message-ID: <4B0BB2A7.5040707@trash.net> (raw)
In-Reply-To: <200911241002.20904.arnd@arndb.de>

Arnd Bergmann wrote:
> On Tuesday 24 November 2009 09:51:19 Patrick McHardy wrote:
>>> +     skb_dst_drop(skb);
>>> +     skb->tstamp.tv64 = 0;
>>> +     skb->pkt_type = PACKET_HOST;
>>> +     skb->protocol = eth_type_trans(skb, dev);
>>> +     skb->mark = 0;
>> skb->mark clearing should stay private to veth since its usually
>> supposed to stay intact. The only exception is packets crossing
>> namespaces, where they should appear like a freshly received skbs.
> 
> But isn't that what we want in macvlan as well when we're
> forwarding from one downstream interface to another?

In the TX direction you can use the mark for TC classification
on the underlying device.

> I did all my testing with macvlan interfaces in separate namespaces
> communicating with each other, so I'd assume that we should always
> clear skb->mark and skb->dst in this function.

Good point, in that case we probably should clear it as well. But
in the non-namespace case the TC classification currently works and
this is consistent with any other virtual device driver, so it
should continue to work.

  reply	other threads:[~2009-11-24 10:17 UTC|newest]

Thread overview: 30+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-11-24  0:56 [PATCHv2 0/4] macvlan: add vepa and bridge mode Arnd Bergmann
2009-11-24  0:56 ` [PATCH 1/4] veth: move loopback logic to common location Arnd Bergmann
2009-11-24  9:51   ` Patrick McHardy
2009-11-24 10:02     ` Arnd Bergmann
2009-11-24 10:17       ` Patrick McHardy [this message]
2009-11-24 10:34         ` Arnd Bergmann
2009-11-24 10:40           ` Patrick McHardy
2009-11-24 13:13             ` Arnd Bergmann
2009-11-24 16:42             ` Eric W. Biederman
2009-11-24 16:56               ` Patrick McHardy
2009-11-24 18:10                 ` Eric W. Biederman
2009-11-24 18:28                   ` Arnd Bergmann
2009-11-24 18:38                   ` Patrick McHardy
2009-11-26 15:21                     ` Arnd Bergmann
2009-11-26 15:33                       ` Patrick McHardy
2009-11-26 16:38                         ` Eric W. Biederman
2009-11-26 17:44                         ` Arnd Bergmann
2009-11-26 21:14                           ` Patrick McHardy
2009-11-24  0:56 ` [PATCH 2/4] macvlan: cleanup rx statistics Arnd Bergmann
2009-11-24  8:15   ` Eric Dumazet
2009-11-24  8:45     ` Arnd Bergmann
2009-11-24  9:28       ` Arnd Bergmann
2009-11-24 10:41   ` Patrick McHardy
2009-11-24  0:56 ` [PATCH 3/4] macvlan: implement bridge, VEPA and private mode Arnd Bergmann
2009-11-24 10:42   ` Patrick McHardy
2009-11-24 12:45     ` Arnd Bergmann
2009-11-24  0:56 ` [PATCH 4/4] macvlan: export macvlan mode through netlink Arnd Bergmann
2009-11-24 10:53   ` Patrick McHardy
2009-11-24 12:57     ` Arnd Bergmann
2009-11-24 13:47       ` Patrick McHardy

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=4B0BB2A7.5040707@trash.net \
    --to=kaber@trash.net \
    --cc=anna.fischer@hp.com \
    --cc=arnd@arndb.de \
    --cc=bridge@lists.linux-foundation.org \
    --cc=davem@davemloft.net \
    --cc=ebiederm@xmission.com \
    --cc=eric.dumazet@gmail.com \
    --cc=evb@yahoogroups.com \
    --cc=gerhard.stenzel@de.ibm.com \
    --cc=herbert@gondor.apana.org.au \
    --cc=jens@linux.vnet.ibm.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=lk-netdev@lk-netdev.nosense.org \
    --cc=netdev@vger.kernel.org \
    --cc=pmullaney@novell.com \
    --cc=shemminger@vyatta.com \
    --cc=virtualization@lists.linux-foundation.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).