netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: David Miller <davem@davemloft.net>
To: macro@linux-mips.org
Cc: ralf@linux-mips.org, netdev@vger.kernel.org,
	linux-mips@linux-mips.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH net-next RESEND 2/2] FDDI: DEC FDDIcontroller 700 TURBOchannel card support
Date: Mon, 28 Apr 2014 12:52:44 -0400 (EDT)	[thread overview]
Message-ID: <20140428.125244.18665502106315120.davem@davemloft.net> (raw)
In-Reply-To: <alpine.LFD.2.11.1404280048540.11598@eddie.linux-mips.org>

From: "Maciej W. Rozycki" <macro@linux-mips.org>
Date: Mon, 28 Apr 2014 12:37:08 +0100 (BST)

>  That however I would like to keep -- I find it particularly valuable and 
> a great advantage of this piece of hardware to be able to tap into all the 
> SMT traffic crossing this adapter, both incoming and outgoing, for 
> educational and diagnostic purposes.  Without this capability a second 
> FDDI station is required to be able to see both traffic streams, and also 
> it has to be exactly the next downstream neighbour or some traffic will 
> undoubtedly be stripped from the ring by intermediate stations.
> 
>  Therefore I would like to retain this capability.  If you're unhappy with 
> tapping in directly, then I think sending them back down the usual receive 
> path would do, although at some performance hit.  So I'd prefer to avoid 
> it if possible -- can you propose an alternative by any chance?
> 
>  Thanks for your review, please let me know how to proceed with the issues 
> that remain open.  I'll send updated code once we've settled, I think 
> there's little point in publishing an update before then.

We're not exporting all of these internals for the unique desires of
one single driver.

      reply	other threads:[~2014-04-28 16:52 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-04-25  9:35 [PATCH net-next RESEND 2/2] FDDI: DEC FDDIcontroller 700 TURBOchannel card support Maciej W. Rozycki
2014-04-27 23:13 ` David Miller
2014-04-28 11:37   ` Maciej W. Rozycki
2014-04-28 16:52     ` David Miller [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=20140428.125244.18665502106315120.davem@davemloft.net \
    --to=davem@davemloft.net \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mips@linux-mips.org \
    --cc=macro@linux-mips.org \
    --cc=netdev@vger.kernel.org \
    --cc=ralf@linux-mips.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).