[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <AANLkTi=BfgD+fFXZMAzz0OAuj46X0dxThTSSB9OmCg-3@mail.gmail.com>
Date: Sat, 28 Aug 2010 01:35:19 -0400
From: Kyle Moffett <kyle@...fetthome.net>
To: Stephen Hemminger <shemminger@...ux-foundation.org>
Cc: "Moffett, Kyle D" <Kyle.D.Moffett@...ing.com>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
"netdev@...r.kernel.org" <netdev@...r.kernel.org>
Subject: Re: [PATCH 2/2] sky2: Add unidirectional fiber link support
On Fri, Aug 27, 2010 at 17:22, Stephen Hemminger
<shemminger@...ux-foundation.org> wrote:
> On Fri, 27 Aug 2010 15:51:58 -0500 "Moffett, Kyle D" <Kyle.D.Moffett@...ing.com> wrote:
>> Do you have any comments or criticisms of the particular "duplex" method of configuring the unidirectional link support?
>
> No that is fine, but the FIB doesn't really understand RX only links so I expect users will do stupid things.
As far as the chipset is concerned, an "rxonly" link would just be a
regular full-duplex forced-mode fiber link. If the user happens to
wire up the "transmit" path on such a link and is then surprised when
the driver is actually able to use that path, that would seem to be
their own problem. I'm considering perhaps fiddling with ARP or
routing behavior over txonly/rxonly links, so I'd like to preserve the
symmetry even if just for documentation purposes or future
optimizations.
When I get any applicable review commentary sorted out and worked
through, in whose tree should I request inclusion of these 2 patches?
Thanks for your comments!
Cheers,
Kyle Moffett
--
To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Powered by blists - more mailing lists