netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Nicolas de Pesloüan" <nicolas.2p.debian@gmail.com>
To: Jiri Pirko <jpirko@redhat.com>
Cc: Stephen Hemminger <shemminger@linux-foundation.org>,
	netdev@vger.kernel.org, davem@davemloft.net, kaber@trash.net,
	fubar@us.ibm.com, eric.dumazet@gmail.com, andy@greyhouse.net,
	xiaosuo@gmail.com, jesse@nicira.com
Subject: Re: [patch net-next-2.6] net: vlan: make non-hw-accel rx path similar to hw-accel
Date: Sun, 03 Apr 2011 11:27:29 +0200	[thread overview]
Message-ID: <4D983D81.2020500@gmail.com> (raw)
In-Reply-To: <20110402182711.GA11885@psychotron.redhat.com>

Le 02/04/2011 20:27, Jiri Pirko a écrit :
> Sat, Apr 02, 2011 at 05:55:24PM CEST, shemminger@linux-foundation.org wrote:
>> On Sat,  2 Apr 2011 12:26:06 +0200
>> Jiri Pirko<jpirko@redhat.com>  wrote:
<snip>
>>> +	rawp = skb->data;
>>> +	if (*(unsigned short *) rawp == 0xFFFF)
>>> +		/*
>>> +		 * This is a magic hack to spot IPX packets. Older Novell
>>> +		 * breaks the protocol design and runs IPX over 802.3 without
>>> +		 * an 802.2 LLC layer. We look for FFFF which isn't a used
>>> +		 * 802.2 SSAP/DSAP. This won't work for fault tolerant netware
>>> +		 * but does for the rest.
>>> +		 */
>>> +		skb->protocol = htons(ETH_P_802_3);
>>> +	else
>>> +		/*
>>> +		 * Real 802.2 LLC
>>> +		 */
>>> +		skb->protocol = htons(ETH_P_802_2);
>>> +}
>>
>> What about doublely tagged packets?
>
> No problem. Once they are untagged and reinjected they are untagged
> again and reinjected again:
>
> ->  __netif_reveive_skb
> vlan_untag
> vlan_do_receive
> ->  __netif_receive_skb
> vlan_untag
> vlan_do_receive

Hi Jiri,

Instead of untagging and reinjecting, wouldn't it be possible to remove all 802.1Q headers in a loop 
and directly deliver the untagged skb? Are there any hw-accel implementations that remove several 
level of tagging?

	Nicolas.

  reply	other threads:[~2011-04-03  9:27 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-04-02 10:26 [patch net-next-2.6] net: vlan: make non-hw-accel rx path similar to hw-accel Jiri Pirko
2011-04-02 15:55 ` Stephen Hemminger
2011-04-02 18:27   ` Jiri Pirko
2011-04-03  9:27     ` Nicolas de Pesloüan [this message]
2011-04-03 13:22       ` Jiri Pirko
2011-04-03 15:23 ` Nicolas de Pesloüan
2011-04-03 20:38   ` Jesse Gross
2011-04-04  6:54     ` Nicolas de Pesloüan
2011-04-04  7:14       ` Jiri Pirko
2011-04-04 19:00         ` Nicolas de Pesloüan
2011-04-04 19:51           ` Eric W. Biederman
2011-04-04 20:29             ` Jiri Pirko
2011-04-04 20:47             ` Nicolas de Pesloüan
2011-04-04 20:50               ` Jesse Gross
2011-04-04 21:04                 ` Nicolas de Pesloüan
2011-04-05  7:25                   ` Jiri Pirko
2011-04-05  7:26               ` Jiri Pirko
2011-04-04 20:30           ` Jiri Pirko
2011-04-04 20:51             ` Nicolas de Pesloüan
2011-04-05  7:19               ` Jiri Pirko

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=4D983D81.2020500@gmail.com \
    --to=nicolas.2p.debian@gmail.com \
    --cc=andy@greyhouse.net \
    --cc=davem@davemloft.net \
    --cc=eric.dumazet@gmail.com \
    --cc=fubar@us.ibm.com \
    --cc=jesse@nicira.com \
    --cc=jpirko@redhat.com \
    --cc=kaber@trash.net \
    --cc=netdev@vger.kernel.org \
    --cc=shemminger@linux-foundation.org \
    --cc=xiaosuo@gmail.com \
    /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).