From: Shashikant Poonia <shashikantpoonia89@gmail.com>
To: users@dpdk.org, dev@dpdk.org
Subject: Re: [dpdk-dev] ixgbe: link status for PF up/down is not updating using LSI DPDK16.11.1 Sample App
Date: Fri, 2 Jun 2017 10:37:22 +0530 [thread overview]
Message-ID: <CAGBa_1DzwYFv2nkbxwNkPXZRVv8KbZo8UjHiYSk6hy6qnKnNCQ@mail.gmail.com> (raw)
In-Reply-To: <CAGBa_1BUQT4TnMz08X_3T_dQTjs=cHERQpCDQmr=inx+8yBbvg@mail.gmail.com>
Hi all, Anybody got a chance to look into ?
BTW, am using below two patches for VF reset on DPDK 16.11
http://dpdk.org/ml/archives/dev/2016-June/040287.html ::lib/librte_ether:
support device reset
http://dpdk.org/ml/archives/dev/2016-June/040290.html
<http://dpdk.org/ml/archives/dev/2016-June/040289.html> ::ixgbe: implement
device reset on VF
Having few queries based above patches.
1) Are above patches are sufficient to reset VF ? Along with 2 patches, do
we need to have more fix ?
2) May know, Why above patches are not submitted, Were there any side
effect of both patches ?
3) Is the patch applicable to DPDK 2.1 also along with mailbox process
patch ?
4) Is there any plan to submit above fixes in latest dpdk code ?
Awaiting for the reply .. Thanks in advance.
On Fri, May 26, 2017 at 6:41 PM, Shashikant Poonia <
shashikantpoonia89@gmail.com> wrote:
> Hi All,
>
>
> I am running Link Status Interrupt(LSI) DPDK sample application to test
> link status by making PF up/down using 'ip link set dev <intface>
> up/down'. I would think, it should trigger 'ixgbe_dev_interrupt_handler()'
> when we do interface up/down. But looks like it is not triggered
> 'ixgbe_dev_interrupt_handler()' to update link status.
>
>
> setup details:
>
> DPDK 16.11.1 LSI sample application
> Host: rhel 7.2 having Intel X540 10G card
> Guest: KVM hypervisor attached VFs
>
> Execute LSI binary on Guest using
> ./link_status_interrupt -c 2 -n 4 -- -q 2 -p 0x3
>
> My main goal to check the link status of VF's on Guest machine, but looks
> like its not updated on PF itself. So once this works then i hope it works
> for VF as well
>
> Please do let me know, whether i am missing any configuraion/patch ? Any
> help would be appreciated
>
>
>
> --
> Regards,
> Shashikant Poonia
>
--
Regards,
Shashikant Poonia
prev parent reply other threads:[~2017-06-02 5:07 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-05-26 13:11 Shashikant Poonia
2017-06-02 5:07 ` Shashikant Poonia [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=CAGBa_1DzwYFv2nkbxwNkPXZRVv8KbZo8UjHiYSk6hy6qnKnNCQ@mail.gmail.com \
--to=shashikantpoonia89@gmail.com \
--cc=dev@dpdk.org \
--cc=users@dpdk.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).