DPDK usage discussions
 help / color / mirror / Atom feed
From: Gadre Nayan <gadrenayan@gmail.com>
To: users@dpdk.org
Subject: [dpdk-users] LSC interrupt thread and normal thread
Date: Thu, 28 Apr 2016 16:37:16 +0530	[thread overview]
Message-ID: <CAKJ7aR6+c7i9L41xtexajj5OKDLRZcZ49ak86uWczxTn8ocpdg@mail.gmail.com> (raw)

Hi,

I have a doubt regarding the LSC interrupt context and normal thread context.

The guide states that: the callback function of the LSC interrupt:

This function should be implemented with care since it will be called
in the interrupt host thread, which is different from the main thread
of its caller.

So suppose I want to propagate an event to signify a link state
change, can I directly call an ioctl to the driver which will then
propagate using netlink to userspace ?

Are the special considerations for the interrupt host thread same as
the considerations for interrupt context and SOFTIRQ in linux kernel ?

Thanks.

                 reply	other threads:[~2016-04-28 11:07 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=CAKJ7aR6+c7i9L41xtexajj5OKDLRZcZ49ak86uWczxTn8ocpdg@mail.gmail.com \
    --to=gadrenayan@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).