From: David Marchand <david.marchand@6wind.com>
To: Adrien Mazarguil <adrien.mazarguil@6wind.com>
Cc: "dev@dpdk.org" <dev@dpdk.org>
Subject: Re: [dpdk-dev] [PATCH 1/3] eal: new interrupt handler type
Date: Tue, 20 Oct 2015 22:25:11 +0200 [thread overview]
Message-ID: <CALwxeUsqh_EEO8XFSEK34cLA6KWYjbUFCez4YVoNtY2oh439rg@mail.gmail.com> (raw)
In-Reply-To: <1444067795-29748-2-git-send-email-adrien.mazarguil@6wind.com>
On Mon, Oct 5, 2015 at 7:56 PM, Adrien Mazarguil <adrien.mazarguil@6wind.com
> wrote:
> From: Nelio Laranjeiro <nelio.laranjeiro@6wind.com>
>
> Add RTE_INTR_HANDLE_EXT handler type for PMDs that do not support VFIO or
> UIO. Those are expected to manage the file descriptor themselves.
>
> Signed-off-by: Nelio Laranjeiro <nelio.laranjeiro@6wind.com>
>
Maybe a title like "eal: allow external interrupt handler" would be better.
Acked-by: David Marchand <david.marchand@6wind.com>
--
David Marchand
next prev parent reply other threads:[~2015-10-20 20:25 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-10-05 17:56 [dpdk-dev] [PATCH 0/3] Add link status notification support to Mellanox PMDs Adrien Mazarguil
2015-10-05 17:56 ` [dpdk-dev] [PATCH 1/3] eal: new interrupt handler type Adrien Mazarguil
2015-10-20 20:25 ` David Marchand [this message]
2015-10-05 17:56 ` [dpdk-dev] [PATCH 2/3] mlx4: handle interrupts Adrien Mazarguil
2015-10-05 17:56 ` [dpdk-dev] [PATCH 3/3] mlx5: " Adrien Mazarguil
2015-10-30 18:57 ` [dpdk-dev] [PATCH v2 0/3] Add link status notification support to Mellanox PMDs Adrien Mazarguil
2015-10-30 18:57 ` [dpdk-dev] [PATCH v2 1/3] eal: new interrupt handler type Adrien Mazarguil
2015-10-30 18:57 ` [dpdk-dev] [PATCH v2 2/3] mlx4: handle interrupts Adrien Mazarguil
2015-10-30 18:57 ` [dpdk-dev] [PATCH v2 3/3] mlx5: " Adrien Mazarguil
2015-11-01 10:32 ` [dpdk-dev] [PATCH v2 0/3] Add link status notification support to Mellanox PMDs Thomas Monjalon
2015-11-02 11:12 ` Adrien Mazarguil
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=CALwxeUsqh_EEO8XFSEK34cLA6KWYjbUFCez4YVoNtY2oh439rg@mail.gmail.com \
--to=david.marchand@6wind.com \
--cc=adrien.mazarguil@6wind.com \
--cc=dev@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).