From: David Miller <davem@davemloft.net>
To: amit.salecha@qlogic.com
Cc: bhutchings@solarflare.com, netdev@vger.kernel.org,
ameen.rahman@qlogic.com, sucheta.chakraborty@qlogic.com
Subject: Re: [PATCHv2 NEXT 1/2] net: add external loopback test in ethtool self test
Date: Thu, 30 Jun 2011 23:58:47 -0700 (PDT) [thread overview]
Message-ID: <20110630.235847.1364630282954525785.davem@davemloft.net> (raw)
In-Reply-To: <1309413650-15952-2-git-send-email-amit.salecha@qlogic.com>
From: amit.salecha@qlogic.com
Date: Wed, 29 Jun 2011 23:00:49 -0700
> From: Amit Kumar Salecha <amit.salecha@qlogic.com>
>
> External loopback test can be performed by application without any driver
> support on normal Ethernet cards.
> But on CNA devices, where multiple functions share same physical port.
> Here internal loopback test and external loopback test can be initiated by
> multiple functions at same time. To co exist all functions, firmware need
> to regulate what test can be run by which function. So before performing external
> loopback test, command need to send to firmware, which will quiescent other functions.
>
> User may not want to run external loopback test always. As special cable need to be
> connected for this test.
> So adding explicit flag in ethtool self test, which will specify interface
> to perform external loopback test.
> ETH_TEST_FL_EXTERNAL_LB: Application set to request external loopback test
> ETH_TEST_FL_EXTERNAL_LB_DONE: Driver ack if test performed
>
> Signed-off-by: Amit Kumar Salecha <amit.salecha@qlogic.com>
Applied.
next prev parent reply other threads:[~2011-07-01 6:58 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-06-30 6:00 [PATCHv2 NEXT 0/2]net: external loopback suport in ethtool amit.salecha
2011-06-30 6:00 ` [PATCHv2 NEXT 1/2] net: add external loopback test in ethtool self test amit.salecha
2011-06-30 13:25 ` Ben Hutchings
2011-07-01 6:58 ` David Miller [this message]
2011-06-30 6:00 ` [PATCHv2 NEXT 2/2] qlcnic: add external loopback support amit.salecha
2011-07-01 6:58 ` David Miller
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=20110630.235847.1364630282954525785.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=ameen.rahman@qlogic.com \
--cc=amit.salecha@qlogic.com \
--cc=bhutchings@solarflare.com \
--cc=netdev@vger.kernel.org \
--cc=sucheta.chakraborty@qlogic.com \
/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).