From: Jerin Jacob <jerin.jacob@caviumnetworks.com>
To: Bruce Richardson <bruce.richardson@intel.com>
Cc: dev@dpdk.org, olivier.matz@6wind.com
Subject: Re: [PATCH 3/5] eventdev: add ring structure for events
Date: Mon, 12 Jun 2017 10:45:47 +0530 [thread overview]
Message-ID: <20170612051546.GA9948@jerin> (raw)
In-Reply-To: <20170607133620.275801-4-bruce.richardson@intel.com>
-----Original Message-----
> Date: Wed, 7 Jun 2017 14:36:18 +0100
> From: Bruce Richardson <bruce.richardson@intel.com>
> To: dev@dpdk.org
> CC: olivier.matz@6wind.com, jerin.jacob@caviumnetworks.com, Bruce
> Richardson <bruce.richardson@intel.com>
> Subject: [PATCH 3/5] eventdev: add ring structure for events
> X-Mailer: git-send-email 2.9.4
>
> Add in a new rte_event_ring structure type and functions to allow events to
> be passed core to core. This is needed because the standard rte_ring type
> only works on pointers, while for events, we want to copy the entire, 16B
> events themselves - not just pointers to them. The code makes extensive use
> of the functions already defined in rte_ring.h
>
> Signed-off-by: Bruce Richardson <bruce.richardson@intel.com>
Thomas,
Should this series applied through dpdk/master or dpdk-next-eventdev/master?
Bruce,
__rte_always_inline macro is now part of master. Good to replace with force_inline.
next prev parent reply other threads:[~2017-06-12 5:16 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-06-07 13:36 [PATCH 0/5] create event rings type Bruce Richardson
2017-06-07 13:36 ` [PATCH 1/5] ring: allow rings with non power-of-2 sizes Bruce Richardson
2017-06-30 9:40 ` Olivier Matz
2017-06-30 11:32 ` Bruce Richardson
2017-06-30 12:24 ` Olivier Matz
2017-06-30 13:59 ` Bruce Richardson
2017-06-07 13:36 ` [PATCH 2/5] test/test: add unit tests for exact size rings Bruce Richardson
2017-06-30 9:42 ` Olivier Matz
2017-06-07 13:36 ` [PATCH 3/5] eventdev: add ring structure for events Bruce Richardson
2017-06-12 5:15 ` Jerin Jacob [this message]
2017-06-12 8:53 ` Bruce Richardson
2017-06-30 13:24 ` Bruce Richardson
2017-06-07 13:36 ` [PATCH 4/5] test/test: add auto-tests for event ring functions Bruce Richardson
2017-06-07 13:36 ` [PATCH 5/5] event/sw: change worker rings to standard event rings Bruce Richardson
2017-06-30 15:06 ` [PATCH v2 0/5] create event rings type Bruce Richardson
2017-06-30 15:06 ` [PATCH v2 1/5] ring: allow rings with non power-of-2 sizes Bruce Richardson
2017-07-03 8:46 ` Olivier Matz
2017-06-30 15:06 ` [PATCH v2 2/5] test/test: add unit tests for exact size rings Bruce Richardson
2017-07-03 8:47 ` Olivier Matz
2017-06-30 15:06 ` [PATCH v2 3/5] eventdev: add ring structure for events Bruce Richardson
2017-07-03 9:52 ` Van Haaren, Harry
2017-06-30 15:06 ` [PATCH v2 4/5] test/test: add auto-tests for event ring functions Bruce Richardson
2017-07-03 12:30 ` Van Haaren, Harry
2017-06-30 15:06 ` [PATCH v2 5/5] event/sw: change worker rings to standard event rings Bruce Richardson
2017-07-03 12:28 ` Van Haaren, Harry
2017-07-03 12:44 ` Jerin Jacob
2017-07-03 13:01 ` Van Haaren, Harry
2017-07-04 5:36 ` Jerin Jacob
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=20170612051546.GA9948@jerin \
--to=jerin.jacob@caviumnetworks.com \
--cc=bruce.richardson@intel.com \
--cc=dev@dpdk.org \
--cc=olivier.matz@6wind.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.