netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: jamal <hadi@cyberus.ca>
To: "Kok, Auke" <auke-jan.h.kok@intel.com>
Cc: Ben Greear <greearb@candelatech.com>,
	Emil Micek <emil.micek@tkrjasek.cz>,
	netdev mailing list <netdev@vger.kernel.org>,
	Jesse <jesse.brandeburg@intel.com>
Subject: Re: change the way e1000 is handling short VLAN frames
Date: Fri, 21 Sep 2007 17:43:26 -0400	[thread overview]
Message-ID: <1190411007.4231.54.camel@localhost> (raw)
In-Reply-To: <46F438F3.5030201@intel.com>

On Fri, 2007-21-09 at 14:34 -0700, Kok, Auke wrote:

> I never saw any bugreports about e1000 not being able to accept vlan packets
> because of this, so I'm quite certain it works OK, feel free to find me a case
> where this isn't so :)

If you tell me it can be done on the rx, i will take your word for it;->
Emil can certainly verify it. 
The tx you certainly have issues - Look at one of the suggestions from
Chris, i think it is resolvable.

cheers,
jamal


  reply	other threads:[~2007-09-21 21:43 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-09-21  7:31 change the way e1000 is handling short VLAN frames Emil Micek
2007-09-21 11:59 ` jamal
2007-09-21 12:50   ` Emil Micek
2007-09-21 13:37     ` jamal
2007-09-21 13:46       ` jamal
2007-09-21 14:27         ` Francesco Fondelli
2007-09-21 15:43         ` Ben Greear
2007-09-21 21:12           ` jamal
2007-09-21 21:18             ` Ben Greear
2007-09-21 21:21             ` Kok, Auke
2007-09-21 21:29               ` jamal
2007-09-21 21:34                 ` Kok, Auke
2007-09-21 21:43                   ` jamal [this message]
2007-09-21 22:02                     ` Chris Leech
2007-09-24  8:40                       ` Emil Micek
2007-09-21 21:27             ` Chris Leech
2007-09-21 21:36               ` jamal
2007-09-21 17:05     ` Brandeburg, Jesse

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=1190411007.4231.54.camel@localhost \
    --to=hadi@cyberus.ca \
    --cc=auke-jan.h.kok@intel.com \
    --cc=emil.micek@tkrjasek.cz \
    --cc=greearb@candelatech.com \
    --cc=jesse.brandeburg@intel.com \
    --cc=netdev@vger.kernel.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).