From: <martin_curran-gray@keysight.com>
To: <users@dpdk.org>
Subject: Re: [dpdk-users] Link Status and Interrupts in 2.2.0
Date: Tue, 26 Apr 2016 06:03:01 +0000 [thread overview]
Message-ID: <22C95CA62CBADB498D32A348F0F073BC116CC91D@wcosexch02k.cos.is.keysight.com> (raw)
In-Reply-To: <22C95CA62CBADB498D32A348F0F073BC116CC81F@wcosexch02k.cos.is.keysight.com>
> Your application needs to make one call to check for current link state after device is started. After that all updates can be done from the LSC interrupt callback.
I made a call from the application, it just keeps getting 0s?
If I change the lsc value to 0, then the call gets the correct value, since it's asking the card, not the global value the callback fills in
I seem to be able to register a handler for the interrupt which gets called, even if lsc is 0?
Then I can call that once at startup, then use the callback????
Seems a little strange?
Thanks for your help Stephen H.
Martin Curran-Gray
next prev parent reply other threads:[~2016-04-26 6:03 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-04-25 11:49 martin_curran-gray
2016-04-25 20:03 ` Stephen Hemminger
2016-04-26 6:03 ` martin_curran-gray [this message]
2016-04-27 9:39 ` Thomas Monjalon
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=22C95CA62CBADB498D32A348F0F073BC116CC91D@wcosexch02k.cos.is.keysight.com \
--to=martin_curran-gray@keysight.com \
--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).