public inbox for netdev@vger.kernel.org
 help / color / mirror / Atom feed
From: Robert Olsson <robert@herjulf.net>
To: David Miller <davem@davemloft.net>
Cc: netdev@vger.kernel.org, robert@herjulf.net
Subject: Diagnostic Monitoring Interface Monitoring (DOM) PATCH 0/5 for net-next-2.6
Date: Mon, 23 Nov 2009 23:45:40 +0100	[thread overview]
Message-ID: <19211.4244.135603.458550@gargle.gargle.HOWL> (raw)


Here are basic support to bring Diagnostic Monitoring Interface Monitoring (DOM)
to Linux this is more or less mandatory when building optical networks.

Optical modules as SFP, SFP+, XFP, GBIC etc holds transceiver and link diagnostic 
data needed to monitor and troubleshoot optical links, Talks to networks cards
via the I2C-bus (DOM lives in memory page 0xA2).

In essential:

Usage example: ethtool -D eth5 

Ext-Calbr: Avr RX-Power: Alarm & Warn: RX_LOS:         Wavelength: 1310 nm
Alarms, warnings in beginning of line, Ie. AH = Alarm High, WL == Warn Low etc
       Temp:  35.9 C                   Thresh: Lo: -12.0/-8.0   Hi: 103.0/110.0 C
       Vcc:  3.33 V                    Thresh: Lo:   3.0/3.0    Hi:   3.7/4.0   V
       Tx-Bias:  13.4 mA               Thresh: Lo:   2.0/4.0    Hi:  70.0/84.0  mA
ALWL   TX-pwr:  -5.9 dBm ( 0.26 mW)    Thresh: Lo:  -4.0/-2.0   Hi:   7.0/8.2   dBm
AHWH   RX-pwr:  -5.0 dBm ( 0.31 mW)    Thresh: Lo: -35.2/-28.0  Hi:  -8.2/-6.0  dBm

Read more in Documentation/networking/dom.txt

It's tested with the igb driver, there is also a patch for the ixgbe driver but I 
haven't any SFP+ with DOM support yet.


There are room for improvements an clean-ups. 

Cheers
						--ro





             reply	other threads:[~2009-11-23 22:45 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-11-23 22:45 Robert Olsson [this message]
2009-11-25  8:18 ` Diagnostic Monitoring Interface Monitoring (DOM) PATCH 0/5 for net-next-2.6 Jeff Kirsher
2009-11-25  9:19   ` Jeff Kirsher
2009-11-25 16:22     ` robert
2009-11-25 20:38       ` Joe Perches
2009-11-26 15:11         ` robert
2009-11-25 16:21   ` robert

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=19211.4244.135603.458550@gargle.gargle.HOWL \
    --to=robert@herjulf.net \
    --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