netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Matheos Worku <Matheos.Worku@Sun.COM>
To: David Miller <davem@davemloft.net>
Cc: Joyce.Yu@Sun.COM, netdev@vger.kernel.org
Subject: Re: [PATCH] [NIU] VLAN does not work with niu driver
Date: Wed, 09 Sep 2009 18:19:00 -0700	[thread overview]
Message-ID: <4AA85404.5020300@sun.com> (raw)
In-Reply-To: <20090909.181033.25374239.davem@davemloft.net>



David Miller wrote:
> From: Matheos Worku <Matheos.Worku@Sun.COM>
> Date: Wed, 09 Sep 2009 18:01:23 -0700
> 
>> The frame type in NIU HW is embedded in a HW header, so it is possible
>> to check the HW header and decide whether to pull up ETH_HLEN or VLAN
>> header size of bytes. However, considering the amount of work required
>> to get and examine the HW header (including endianess issues), we
>> thought pulling up 64 bytes by default (as used in cassini.c) would be
>> efficient.
> 
> Well, it was 64 in early versions of the driver, and I decreased it
> down to ETH_HLEN.
> 
> The less the better since for forwarding applications anything past
> the IPV4 header pulled is going to be a waste of CPU cache lines and
> thus negatively effect forwarding rates.
> 
> That's why I asked if this change was performance regression tested,
> because I know it's going to slow down forwarding rates for small
> packets.
Dave,

We did throughput testing (netperf) and didn't notice any performance 
degradation. We haven't done forwarding testing however.

We can work on a version which implements HW header checking and do 
pullup accordingly.


Regards,
Matheos

> --
> To unsubscribe from this list: send the line "unsubscribe netdev" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html

  reply	other threads:[~2009-09-10  1:20 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-09-09 21:10 [PATCH] [NIU] VLAN does not work with niu driver Joyce Yu
2009-09-09 21:35 ` Stephen Hemminger
2009-09-10  0:16   ` David Miller
2009-09-10  0:15 ` David Miller
2009-09-10  1:01   ` Matheos Worku
2009-09-10  1:10     ` David Miller
2009-09-10  1:19       ` Matheos Worku [this message]
2009-09-10  1:44         ` David Miller
2009-09-10  1:48           ` Matheos Worku
2009-09-10 16:35         ` Rick Jones
  -- strict thread matches above, loose matches on Subject: below --
2009-10-12 23:26 Joyce Yu
2009-10-12 23:52 ` David Miller
2009-10-13  5:41 Joyce Yu
2009-10-13  6:22 ` David Miller
2009-10-13 21:27 Joyce Yu
2009-10-13 22:12 ` David Miller
2009-10-20  0:28 ` David Miller
2009-10-15 19:16 Joyce Yu
2009-10-21 18:02 Joyce Yu
2009-10-21 23:09 ` David Miller
2009-10-21 23:28   ` Joyce Yu
2009-10-22  0:19     ` David Miller

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=4AA85404.5020300@sun.com \
    --to=matheos.worku@sun.com \
    --cc=Joyce.Yu@Sun.COM \
    --cc=davem@davemloft.net \
    --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).