All of lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Monjalon <thomas.monjalon@6wind.com>
To: Shahaf Shuler <shahafs@mellanox.com>, ferruh.yigit@intel.com
Cc: dev@dpdk.org, adrien.mazarguil@6wind.com, nelio.laranjeiro@6wind.com
Subject: Re: [PATCH 1/2] eal_interrupts: support external rxq interrupt handlers
Date: Thu, 09 Mar 2017 19:10:22 +0100	[thread overview]
Message-ID: <3002919.bpld94t7Wf@xps13> (raw)
In-Reply-To: <1486562252-15307-2-git-send-email-shahafs@mellanox.com>

2017-02-08 15:57, Shahaf Shuler:
>  /**
> + * It deletes registered eventfds.
> + *
> + * @param intr_handle
> + *   Pointer to the interrupt handle.
> + */
> +void
> +rte_intr_free_epoll_fd(struct rte_intr_handle *intr_handle);

This patch looks OK except a miss in the EAL map files for this new function.
The title should be "eal/linux: support external Rx interrupt"

I think this patch should target next-net.
Please Ferruh, take care of this patchset. Thanks

  reply	other threads:[~2017-03-09 18:10 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-02-08 13:57 [PATCH 0/2] net/mlx5 add rxq interrupt support Shahaf Shuler
2017-02-08 13:57 ` [PATCH 1/2] eal_interrupts: support external rxq interrupt handlers Shahaf Shuler
2017-03-09 18:10   ` Thomas Monjalon [this message]
2017-03-12  8:30     ` Shahaf Shuler
2017-03-14 12:32       ` Ferruh Yigit
2017-02-08 13:57 ` [PATCH 2/2] net/mlx5: support user space rxq interrupt event Shahaf Shuler
2017-02-09 14:48 ` [PATCH 0/2] net/mlx5 add rxq interrupt support Ferruh Yigit
2017-02-12  7:08   ` Shahaf Shuler
2017-02-21 11:40 ` Shahaf Shuler
2017-02-28  7:29   ` Shahaf Shuler
2017-03-14 13:03 ` [PATCH v2 " Shahaf Shuler
2017-03-14 13:03   ` [PATCH v2 1/2] eal/linux: support external Rx interrupt Shahaf Shuler
2017-03-14 16:38     ` Yongseok Koh
2017-03-14 18:06       ` Ferruh Yigit
2017-03-14 13:03   ` [PATCH v2 2/2] net/mlx5: support user space rxq interrupt event Shahaf Shuler
2017-03-14 16:39     ` Yongseok Koh

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=3002919.bpld94t7Wf@xps13 \
    --to=thomas.monjalon@6wind.com \
    --cc=adrien.mazarguil@6wind.com \
    --cc=dev@dpdk.org \
    --cc=ferruh.yigit@intel.com \
    --cc=nelio.laranjeiro@6wind.com \
    --cc=shahafs@mellanox.com \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.