mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: David Miller <davem@davemloft.net>
To: shemminger@linux-foundation.org
Cc: greearb@candelatech.com,
	djohnson+linux-kernel@sw.starentnetworks.com,
	linux-kernel@vger.kernel.org, netdev@vger.kernel.org,
	bguo@sw.starentnetworks.com
Subject: Re: expected behavior of PF_PACKET on NETIF_F_HW_VLAN_RX device?
Date: Wed, 31 Oct 2007 21:50:25 -0700 (PDT)	[thread overview]
Message-ID: <20071031.215025.195350296.davem@davemloft.net> (raw)
In-Reply-To: <47292A99.5070805@linux-foundation.org>

From: Stephen Hemminger <shemminger@linux-foundation.org>
Date: Wed, 31 Oct 2007 18:23:37 -0700

> The code in AF_PACKET should fix the skb before passing to user
> space so that there is no difference between accel and non-accel
> hardware.  Internal choices shouldn't leak to user space.  Ditto,
> the receive checksum offload should be fixed up as well.

The hardware has stripped the VLAN header completely and has not
provided it to us at all.

In my opinion trying to cobble one up by hand using the known TAG is
worse than not providing a VLAN header at all.

  parent reply	other threads:[~2007-11-01  4:50 UTC|newest]

Thread overview: 32+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-10-31 18:43 Dave Johnson
2007-10-31 19:33 ` Stephen Hemminger
2007-11-01  1:06   ` Ben Greear
2007-11-01  1:10     ` David Miller
2007-11-01  1:23     ` Stephen Hemminger
2007-11-01  1:31       ` Ben Greear
2007-11-01  4:50       ` David Miller [this message]
2007-11-01 15:04         ` Ben Greear
2007-11-01 21:35           ` David Miller
2007-11-01 21:36           ` Dave Johnson
2007-11-01 21:48             ` Rick Jones
2007-11-01 21:59               ` David Miller
2007-11-01 22:04                 ` Rick Jones
2007-11-01 22:07                   ` David Miller
2007-11-01 23:26                     ` Rick Jones
2007-11-05 17:46                       ` [PATCH 1/2] NET: Re-add VLAN tag for devices incapable of keeping it Dave Johnson
2007-11-05 18:00                         ` Patrick McHardy
2007-11-05 23:15                           ` David Miller
2007-11-06  0:21                             ` Patrick McHardy
2007-11-06  0:35                               ` David Miller
2007-11-06 18:03                               ` Krzysztof Halasa
2007-11-06 18:56                                 ` Ben Greear
2007-11-06 20:08                                   ` Krzysztof Halasa
2007-11-06 23:55                                 ` Patrick McHardy
2007-11-05 17:47                       ` [PATCH 2/2] " Dave Johnson
2007-11-06  2:39                         ` Ramkrishna Vepa
2007-11-06 18:28                           ` Ramkrishna Vepa
2007-11-06 18:34                             ` Dave Johnson
2007-11-01 21:58             ` expected behavior of PF_PACKET on NETIF_F_HW_VLAN_RX device? David Miller
2007-11-02 18:08             ` Dave Johnson
2007-11-02 21:20               ` David Miller
2007-11-02 21:52               ` Michael Chan

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=20071031.215025.195350296.davem@davemloft.net \
    --to=davem@davemloft.net \
    --cc=bguo@sw.starentnetworks.com \
    --cc=djohnson+linux-kernel@sw.starentnetworks.com \
    --cc=greearb@candelatech.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=netdev@vger.kernel.org \
    --cc=shemminger@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

Powered by JetHome