All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jerin Jacob <jerin.jacob@caviumnetworks.com>
To: Honnappa Nagarahalli <honnappa.nagarahalli@arm.com>
Cc: dev@dpdk.org, gavin.hu@arm.com, nd@arm.com
Subject: Re: [RFC] queue: introduce queue APIs and driver framework
Date: Wed, 27 Jun 2018 21:49:49 +0530	[thread overview]
Message-ID: <20180627161947.GA28037@jerin> (raw)
In-Reply-To: <1530115574-102162-1-git-send-email-honnappa.nagarahalli@arm.com>

-----Original Message-----
> Date: Wed, 27 Jun 2018 11:06:13 -0500
> From: Honnappa Nagarahalli <honnappa.nagarahalli@arm.com>
> To: dev@dpdk.org
> CC: honnappa.nagarahalli@arm.com, gavin.hu@arm.com, nd@arm.com
> Subject: [dpdk-dev] [RFC] queue: introduce queue APIs and driver framework
> X-Mailer: git-send-email 2.7.4
> 
> 
> DPDK offers pipeline model of packet processing. One of the key
> components of this model is the core to core packet exchange.
> rte_ring and rte_event_ring functions are 2 methods provided
> currently for core to core communication. However, these two
> do not separate the APIs from implementation. This does not
> allow using hardware queue implementations in pipeline model.
> This change adds queue APIs and driver framework so that
> HW queues can be used for core to core communication in
> pipeline model.
> When different implementations (ex: HW queues and rte_ring) are used

Just to understand, Do you have any HW in mind where it can do
generic multi producer/multi consumer queue operations for core to core
in HW as offload.



> for the same object in different platforms, it is important to
> make sure that the application is portable. Hence features of
> different implementations must be elevated to the API level, so that
> the application writers can make the right choice.
> Currently, basic APIs are created, will add more required APIs
> as this progresses.
> 
> Honnappa Nagarahalli (1):
>   queue: introduce queue APIs and driver framework
> 
>  lib/librte_queue/rte_queue.c        | 122 ++++++++++++++++++++++
>  lib/librte_queue/rte_queue.h        | 200 ++++++++++++++++++++++++++++++++++++
>  lib/librte_queue/rte_queue_driver.h | 157 ++++++++++++++++++++++++++++
>  3 files changed, 479 insertions(+)
>  create mode 100644 lib/librte_queue/rte_queue.c
>  create mode 100644 lib/librte_queue/rte_queue.h
>  create mode 100644 lib/librte_queue/rte_queue_driver.h
> 
> --
> 2.7.4
> 

  parent reply	other threads:[~2018-06-27 16:20 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-06-27 16:06 [RFC] queue: introduce queue APIs and driver framework Honnappa Nagarahalli
2018-06-27 16:06 ` Honnappa Nagarahalli
2018-06-27 16:19 ` Jerin Jacob [this message]
2018-07-11  2:02   ` Honnappa Nagarahalli
2018-07-11  6:51     ` Jerin Jacob
2018-07-16  2:51       ` Honnappa Nagarahalli

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=20180627161947.GA28037@jerin \
    --to=jerin.jacob@caviumnetworks.com \
    --cc=dev@dpdk.org \
    --cc=gavin.hu@arm.com \
    --cc=honnappa.nagarahalli@arm.com \
    --cc=nd@arm.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.