All of lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Monjalon <thomas@monjalon.net>
To: Jingjing Wu <jingjing.wu@intel.com>
Cc: dev@dpdk.org, jianfeng.tan@intel.com, shreyansh.jain@nxp.com,
	hemant.agrawal@nxp.com, santosh.shukla@caviumnetworks.com,
	Tomasz Duszynski <tdu@semihalf.com>,
	Jacek Siuda <jck@semihalf.com>,
	jerin.jacob@caviumnetworks.com
Subject: Re: [PATCH v3] eal: add counter size for efd clean
Date: Wed, 11 Oct 2017 15:11:03 +0200	[thread overview]
Message-ID: <4513487.fCd9laRvq9@xps> (raw)
In-Reply-To: <1503540656-104421-1-git-send-email-jingjing.wu@intel.com>

Hi,

24/08/2017 04:10, Jingjing Wu:
>         } else if (intr_handle->type == RTE_INTR_HANDLE_VDEV) {
> -               /* do nothing, and let vdev driver to initialize this struct */
> +               /* only check, initialization would be done in vdev driver.*/
> +               if (intr_handle->efd_counter_size >
> +                   sizeof(union rte_intr_read_buffer)) {
> +                       RTE_LOG(ERR, EAL, "the efd_counter_size is oversized");
> +                       return -EINVAL;
> +               }

How interrupts are working with other buses?

Is it something we should manage in bus drivers code?

  parent reply	other threads:[~2017-10-11 13:11 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-08-11  8:34 [PATCH] eal: add counter size for efd clean Jingjing Wu
2017-08-13 15:03 ` [PATCH v2] " Jingjing Wu
2017-08-14 20:06   ` Tan, Jianfeng
2017-08-24  2:10   ` [PATCH v3] " Jingjing Wu
2017-09-04  2:49     ` Tan, Jianfeng
2017-11-07  0:41       ` Thomas Monjalon
2017-10-11 13:11     ` Thomas Monjalon [this message]
2017-10-16 10:29       ` Wu, Jingjing
2017-10-16 10:45         ` Thomas Monjalon
2017-10-24 13:38           ` Wu, Jingjing
2017-10-31 13:25             ` Wu, Jingjing

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=4513487.fCd9laRvq9@xps \
    --to=thomas@monjalon.net \
    --cc=dev@dpdk.org \
    --cc=hemant.agrawal@nxp.com \
    --cc=jck@semihalf.com \
    --cc=jerin.jacob@caviumnetworks.com \
    --cc=jianfeng.tan@intel.com \
    --cc=jingjing.wu@intel.com \
    --cc=santosh.shukla@caviumnetworks.com \
    --cc=shreyansh.jain@nxp.com \
    --cc=tdu@semihalf.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.