All of lore.kernel.org
 help / color / mirror / Atom feed
From: Eric Dumazet <eric.dumazet@gmail.com>
To: Sreenivasa Honnur <Sreenivasa.Honnur@neterion.com>
Cc: davem@davemloft.net, netdev@vger.kernel.org, support@neterion.com
Subject: Re: [net-next-2.6 PATCH 6/9] vxge: Check if FCS stripping is disabled by the firmware.
Date: Mon, 05 Oct 2009 15:04:32 +0200	[thread overview]
Message-ID: <4AC9EEE0.5000601@gmail.com> (raw)
In-Reply-To: <Pine.GSO.4.10.10910050755480.9377-100000@guinness>

Sreenivasa Honnur a écrit :
> - Added a function to check if FCS stripping is disabled by the firmware, if
>   it is not disabled fail driver load.
> 
> - By default FCS stripping is disabled by the firmware. With this assumption
>   driver decrements the indicated packet length by 4 bytes(FCS length).
> 
> - This patch ensures that FCS stripping is disabled during driver load time.
> 
> Signed-off-by: Sreenivasa Honnur <sreenivasa.honnur@neterion.com>

What the big deal about FCS not being stripped ?

Denying driver load for this litle detail seems very hard.
You could issue a warning if there is a performance hit, but allow the driver
to function.

If this adapter has the ability to disable/enable it at firmware level,
you might replace

pkt_length -= ETH_FCS_LEN;

by :

pkt_length -= adapter->fcs_length;  

Granted you initialized adapter->fcs_length to 0 or 4 depending on firmware setup.



  reply	other threads:[~2009-10-05 13:05 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-10-05 11:56 [net-next-2.6 PATCH 6/9] vxge: Check if FCS stripping is disabled by the firmware Sreenivasa Honnur
2009-10-05 13:04 ` Eric Dumazet [this message]
2009-10-05 16:44   ` Ben Greear
2009-10-06  6:41   ` Ramkrishna Vepa
2009-10-06  6:47     ` Eric Dumazet
  -- strict thread matches above, loose matches on Subject: below --
2009-10-05  9:11 Sreenivasa Honnur

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=4AC9EEE0.5000601@gmail.com \
    --to=eric.dumazet@gmail.com \
    --cc=Sreenivasa.Honnur@neterion.com \
    --cc=davem@davemloft.net \
    --cc=netdev@vger.kernel.org \
    --cc=support@neterion.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.