All of lore.kernel.org
 help / color / mirror / Atom feed
From: Ben Hutchings <bhutchings@solarflare.com>
To: Florian Fainelli <florian@openwrt.org>
Cc: <eunb.song@samsung.com>, <netdev@vger.kernel.org>
Subject: Re: Fwd: [PATCH] phydev: Add sysctl variable for polling interval of phy
Date: Mon, 11 Mar 2013 20:39:35 +0000	[thread overview]
Message-ID: <1363034375.2608.83.camel@bwh-desktop.uk.solarflarecom.com> (raw)
In-Reply-To: <513DB5C9.9020807@openwrt.org>

On Mon, 2013-03-11 at 11:45 +0100, Florian Fainelli wrote:
> Hello,
> 
> On 03/11/2013 12:44 AM, EUNBONG SONG wrote:
> >
> >  From d55a22be52e5a768409aa0999d6636cdfc369676 Mon Sep 17 00:00:00 2001
> > From: eunbonsong
> > Date: Sun, 10 Mar 2013 04:57:39 -0700
> > Subject: [PATCH] phydev: Add sysctl variable for polling interval of phy state
> >
> > This adds a dev.phy.phy_poll_interval sysctl variable. This value is represented in milliseconds.
> > And phy_state_machine() is scheduled as this variable.
> > I think HZ is enough for PC. But sometimes especially in network devices
> > such as switches,routers, needs more granularity for detecting phy state change.
> 
> This patch should be submitted according to the rules described in: 
> https://www.kernel.org/doc/Documentation/SubmittingPatches
> 
> Besides that, I do not think that a system-wide knob here is 
> appropriate, you may rather introduce a new ethtool ioctl() to change 
> the PHY device polling interval on a per-PHY device basis.

That sounds like the right place - if it's really necessary to make this
configurable.

> Having said that don't your devices support a dedicated PHY interrupt 
> line? This would definitively be the way to get better latency with 
> respect to PHY events reported back to the host.
[...]

It's nice to have working link interrupts, but they're apparently easy
to get wrong and it just doesn't hurt that much to poll.  They never
worked properly on SFC4000 boards, and polling once a second was good
enough in practice.

Ben.

-- 
Ben Hutchings, Staff Engineer, Solarflare
Not speaking for my employer; that's the marketing department's job.
They asked us to note that Solarflare product names are trademarked.

      reply	other threads:[~2013-03-11 20:39 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-03-10 23:44 Fwd: [PATCH] phydev: Add sysctl variable for polling interval of phy EUNBONG SONG
2013-03-11 10:45 ` Florian Fainelli
2013-03-11 20:39   ` Ben Hutchings [this message]

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=1363034375.2608.83.camel@bwh-desktop.uk.solarflarecom.com \
    --to=bhutchings@solarflare.com \
    --cc=eunb.song@samsung.com \
    --cc=florian@openwrt.org \
    --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 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.