From: "Tu, Lijuan" <lijuan.tu@intel.com>
To: "Jiale, SongX" <songx.jiale@intel.com>, "dts@dpdk.org" <dts@dpdk.org>
Subject: Re: [dts] [PATCH V2] tests/link_status_interrupt: close nic link-down-on-close off
Date: Mon, 25 Oct 2021 06:37:11 +0000 [thread overview]
Message-ID: <1f8bed50cee641b695a65ef549faa94f@intel.com> (raw)
In-Reply-To: <BN0PR11MB574369AB412ABEA91792B917E7839@BN0PR11MB5743.namprd11.prod.outlook.com>
> -----Original Message-----
> From: Jiale, SongX <songx.jiale@intel.com>
> Sent: 2021年10月25日 13:34
> To: Tu, Lijuan <lijuan.tu@intel.com>; dts@dpdk.org
> Subject: RE: [dts] [PATCH V2] tests/link_status_interrupt: close nic link-down-on-
> close off
>
> some network cards do not have link-down-on-close, such as niantic, etc., but
> using verify() to make assertions in the code will cause case failed
I saw it is checked as bellowing:
> > - elif not res:
> > - self.logger.info("NIC %s might not support this case" %
> intf)"
>
> Regards,
> Song Jiale
>
> > -----Original Message-----
> > From: Tu, Lijuan <lijuan.tu@intel.com>
> > Sent: Monday, October 25, 2021 11:52 AM
> > To: Jiale, SongX <songx.jiale@intel.com>; dts@dpdk.org
> > Cc: Jiale, SongX <songx.jiale@intel.com>
> > Subject: RE: [dts] [PATCH V2] tests/link_status_interrupt: close nic
> > link-down-on-close off
> >
> >
> >
> > > -----Original Message-----
> > > From: dts <dts-bounces@dpdk.org> On Behalf Of Jiale Song
> > > Sent: 2021年10月11日 11:42
> > > To: dts@dpdk.org
> > > Cc: Jiale, SongX <songx.jiale@intel.com>
> > > Subject: [dts] [PATCH V2] tests/link_status_interrupt: close nic
> > > link-down-on- close off
> > >
> > > some nics do not support this detection function, delete the check
> > > and directly close nic link-down-on-close
> > >
> >
> > The check have deal with the situation that some nics might be not support it.
> > So I don't think there is any need for your patch.
> >
> > > Signed-off-by: Jiale Song <songx.jiale@intel.com>
> > > ---
> > > tests/TestSuite_link_status_interrupt.py | 19 ++-----------------
> > > 1 file changed, 2 insertions(+), 17 deletions(-)
> > >
> > > diff --git a/tests/TestSuite_link_status_interrupt.py
> > > b/tests/TestSuite_link_status_interrupt.py
> > > index 5590d94..861ca50 100755
> > > --- a/tests/TestSuite_link_status_interrupt.py
> > > +++ b/tests/TestSuite_link_status_interrupt.py
> > > @@ -70,22 +70,6 @@ class TestLinkStatusInterrupt(TestCase):
> > > self.basic_intr_mode = ["msix", "legacy"]
> > > if self.drivername == "vfio-pci":
> > > self.basic_intr_mode.append("msi")
> > > - self.intfs = [self.tester.get_interface(self.tester.get_local_port(i)) for i
> > in
> > > self.dut_ports]
> > > - # check link-down-on-close flag
> > > - self.flag = "link-down-on-close"
> > > - for intf in self.intfs:
> > > - check_flag = "ethtool --show-priv-flags %s" % intf
> > > - set_flag = "ethtool --set-priv-flags %s %s on" % (intf, self.flag)
> > > - out = self.tester.send_expect(check_flag, "#")
> > > - p = re.compile('%s\s+:\s+(\w+)' % self.flag)
> > > - res = re.search(p, out).group(1)
> > > - if res == "off":
> > > - self.tester.send_expect(set_flag, "#")
> > > - time.sleep(0.5)
> > > - out = self.tester.send_expect(check_flag, "#")
> > > - self.verify(re.search(p, out).group(1) == "on", "set %s %s
> > on failed" %
> > > (intf, self.flag))
> > > - elif not res:
> > > - self.logger.info("NIC %s might not support this case" %
> > intf)
> > >
> > > def set_link_status_and_verify(self, dutPort, status):
> > > """
> > > @@ -209,6 +193,7 @@ class TestLinkStatusInterrupt(TestCase):
> > > """
> > > Run after each test suite.
> > > """
> > > + self.intfs =
> > > + [self.tester.get_interface(self.tester.get_local_port(i)) for i in
> > > + self.dut_ports]
> > > if self.dut.get_os_type() != 'freebsd':
> > > for intf in self.intfs:
> > > - self.tester.send_expect("ethtool --set-priv-flags %s %s
> > off" % (intf,
> > > self.flag), "#", 10)
> > > + self.tester.send_expect("ethtool --set-priv-flags
> > > + %s link-down-on-close off" % intf, "# ")
> > > --
> > > 2.17.1
> >
>
next prev parent reply other threads:[~2021-10-25 6:37 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-10-11 3:42 Jiale Song
2021-10-25 3:52 ` Tu, Lijuan
[not found] ` <BN0PR11MB574369AB412ABEA91792B917E7839@BN0PR11MB5743.namprd11.prod.outlook.com>
2021-10-25 6:37 ` Tu, Lijuan [this message]
-- strict thread matches above, loose matches on Subject: below --
2021-10-09 9:00 Jiale Song
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=1f8bed50cee641b695a65ef549faa94f@intel.com \
--to=lijuan.tu@intel.com \
--cc=dts@dpdk.org \
--cc=songx.jiale@intel.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).