DPDK usage discussions
 help / color / mirror / Atom feed
From: Kapil Adhikesavalu <kapil20084@gmail.com>
To: users@dpdk.org
Subject: [dpdk-users] DPDK port interrupt based link state notification
Date: Tue, 23 Aug 2016 14:39:03 +0530	[thread overview]
Message-ID: <CAAu6pRdi_trpvgz08zRghLXzFdvwv-SdFAVT9PByEeafg_dGjg@mail.gmail.com> (raw)

Hi,

I using DPDK with OVS and looking for a way to get interrupt based link
state notifications for dpdk type ports. As its dpdk port, i believe netlink
socket for RTMGRP_LINK is not going to work.
what is the recommended way to get link state notifications for dpdk ports?

i came across "link status interrupt sample application", which is
providing what i am looking for. http://dpdk.org/doc/guides-16.
04/sample_app_ug/link_status_intr.html

How can i use this application along with openvswitch; should i write some
code within ovs to register for ISR ? or is there a another way i can run
this as a separate application without modifying ovs.

when i tried to run OVS with dpdk and link status app, rte_config was
locked by ovs.
[root@localhost build]# ./link_status_interrupt -c f -n 4 --  -p ffff
EAL: Detected lcore 0 as core 0 on socket 0
EAL: Detected lcore 1 as core 1 on socket 0
EAL: Detected lcore 2 as core 2 on socket 0
EAL: Detected lcore 3 as core 3 on socket 0
EAL: Detected lcore 4 as core 4 on socket 0
EAL: Detected lcore 5 as core 5 on socket 0
EAL: Detected lcore 6 as core 6 on socket 0
EAL: Detected lcore 7 as core 7 on socket 0
EAL: Support maximum 128 logical core(s) by configuration.
EAL: Detected 8 lcore(s)
EAL: Error - exiting with code: 1
  Cause: Cannot create lock on '/var/run/.rte_config'. Is another primary
process running?

Thanks
kapil.

             reply	other threads:[~2016-08-23  9:09 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-08-23  9:09 Kapil Adhikesavalu [this message]
2016-08-23 10:27 ` anupam kapoor
     [not found] ` <87r39fiybp.fsf@fatcat.parallelwireless>
2016-08-23 10:38   ` Kapil Adhikesavalu
2016-08-23 10:48     ` anupam kapoor
2016-08-23 10:58       ` Kapil Adhikesavalu

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=CAAu6pRdi_trpvgz08zRghLXzFdvwv-SdFAVT9PByEeafg_dGjg@mail.gmail.com \
    --to=kapil20084@gmail.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).