netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Richard Cochran <richardcochran@gmail.com>
To: netdev@vger.kernel.org
Subject: Configuring synchronous ethernet with ethtool?
Date: Tue, 17 Mar 2015 17:11:28 +0100	[thread overview]
Message-ID: <20150317161128.GA8793@localhost.localdomain> (raw)

Dear list,

I need to configure Synchronous Ethernet (SyncE) on a per-port basis
for a current project.  So, I have been thinking about how best to
implement SyncE.  My first idea is to make this into a new ethtool
operation, but I would like to get some feedback about the direction.

Apart from ITU-T G.8261, 8262, and 8264, which are not too helpful, I
could hardly find any documentation at all about how SyncE is supposed
to work.  My current understanding is limited to:

* 100 Mbit

  - Each link partner generates its own transmit clocks.

  - There is at least one 100 Mbit PHY that allows using the recovered
    clock from the link partner for the PHY's own transmit clock.
    (SyncE slave mode)

* 1000 Mbit

  - With 1000 Mbit, only one of the link partners generates a
    clock. The decision of which link partner becomes the clock master
    is a normal part of the Gigabit protocol.

  - One switch I have worked with has per-port bits that allow setting
    MASTER/SLAVE and MANUAL/PREFERRED.  I am not sure what the
    "preferred" modes does.

So, my current idea is to have an ethtool option to set the SyncE mode
to one of:

- master (1000 Mbit only)
- slave
- none

I am not sure whether the manual/preferred thing makes any sense.
Maybe someone has insight into this?

Thoughts?

Thanks,
Richard

             reply	other threads:[~2015-03-17 16:11 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-03-17 16:11 Richard Cochran [this message]
2015-04-04 13:59 ` Configuring synchronous ethernet with ethtool? Ben Hutchings
2015-04-04 20:03   ` Richard Cochran
2015-04-04 22:55     ` Ben Hutchings

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=20150317161128.GA8793@localhost.localdomain \
    --to=richardcochran@gmail.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).