netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Ben Greear <greearb@candelatech.com>
To: "Fujinaka, Todd" <todd.fujinaka@intel.com>
Cc: Benny Amorsen <benny+usenet@amorsen.dk>,
	"Brandeburg, Jesse" <jesse.brandeburg@intel.com>,
	Jesper Dangaard Brouer <hawk@comx.dk>,
	"e1000-devel@lists.sourceforge.net"
	<e1000-devel@lists.sourceforge.net>,
	"netdev@vger.kernel.org" <netdev@vger.kernel.org>
Subject: Re: [E1000-devel] ixgbe: Unsupported SFP+ modules on 10Gbit/s X520-DA2 NIC?
Date: Wed, 18 Jan 2012 14:40:47 -0800	[thread overview]
Message-ID: <4F174A6F.8050002@candelatech.com> (raw)
In-Reply-To: <9B4A1B1917080E46B64F07F2989DADD621FC38@ORSMSX102.amr.corp.intel.com>

On 01/18/2012 02:21 PM, Fujinaka, Todd wrote:
>
> -----Original Message-----
> From: Benny Amorsen [mailto:benny+usenet@amorsen.dk]
> Sent: Wednesday, January 18, 2012 1:45 PM
> To: Brandeburg, Jesse
> Cc: Jesper Dangaard Brouer; e1000-devel@lists.sourceforge.net; netdev@vger.kernel.org
> Subject: Re: [E1000-devel] ixgbe: Unsupported SFP+ modules on 10Gbit/s X520-DA2 NIC?
>
> Jesse Brandeburg<jesse.brandeburg@intel.com>  writes:
>
>> For X520 adapters, the documentation[1] states that which SFP+
>> adapters are/are not supported.  Direct attach cables are also
>> supported.
>>
>> [1]
>> http://www.intel.com/support/network/adapter/pro100/sb/CS-030612.htm
>
> I can't believe that locked optics have now arrived on commodity hardware. I have been trying to migrate to all-Intel networking at work; that effort is certainly on hold now.
>
>
> That's up to you. There's "locked" and there's "locked". I'm surprised
> that Benny and Jesper haven't looked at the driver to see where the
> messages come from.

As a datapoint:  We had a customer trying to use a non-supported
SFP+ module in an 82599 NIC, and they hacked the driver to over-rule
the exclusion.  It sort of worked for them, but never well, and never
at any decent throughput.

Now, I have no idea if their SFP+ was decent or not, but at least in
some cases, just over-riding the driver doesn't fix things.

It does seem like Intel could offer a module option to easily over-ride the
SFP+ exclusion for folks that wanted to test new SFP+ modules for them,
however.

Thanks,
Ben

-- 
Ben Greear <greearb@candelatech.com>
Candela Technologies Inc  http://www.candelatech.com

  reply	other threads:[~2012-01-18 22:41 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-01-18 11:30 ixgbe: Unsupported SFP+ modules on 10Gbit/s X520-DA2 NIC? Jesper Dangaard Brouer
2012-01-18 17:13 ` Jesse Brandeburg
2012-01-18 20:00   ` Jesper Dangaard Brouer
2012-01-18 21:45   ` Benny Amorsen
2012-01-18 22:19     ` Jesper Dangaard Brouer
2012-01-18 22:43       ` Ben Greear
2012-01-19 14:46       ` [PATCH RFC] ixgbe: Module param "allow_any_sfp" for allowing unsupported SFP+ modules Jesper Dangaard Brouer
2012-01-20  1:12         ` Jeff Kirsher
2012-01-18 22:21     ` [E1000-devel] ixgbe: Unsupported SFP+ modules on 10Gbit/s X520-DA2 NIC? Fujinaka, Todd
2012-01-18 22:40       ` Ben Greear [this message]
2012-01-19 11:50         ` David Lamparter
2012-01-19  1:12       ` [E1000-devel] " Chuck Anderson
2012-01-19  2:55         ` Simon Chen

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=4F174A6F.8050002@candelatech.com \
    --to=greearb@candelatech.com \
    --cc=benny+usenet@amorsen.dk \
    --cc=e1000-devel@lists.sourceforge.net \
    --cc=hawk@comx.dk \
    --cc=jesse.brandeburg@intel.com \
    --cc=netdev@vger.kernel.org \
    --cc=todd.fujinaka@intel.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).