DPDK patches and discussions
 help / color / mirror / Atom feed
From: Jerin Jacob <jerinjacobk@gmail.com>
To: Honnappa Nagarahalli <Honnappa.Nagarahalli@arm.com>
Cc: Mattias Rönnblom <mattias.ronnblom@ericsson.com>,
	 "jerinj@marvell.com" <jerinj@marvell.com>,
	"dev@dpdk.org" <dev@dpdk.org>, nd <nd@arm.com>
Subject: Re: [dpdk-dev] [PATCH] event/dsw: use custom element size ring for control
Date: Tue, 28 Jan 2020 11:30:54 +0530
Message-ID: <CALBAE1PbsiXcXgkFv9EC1Hc3UTAJbUZ_q_htfnqmSG_cvvNvqQ@mail.gmail.com> (raw)
In-Reply-To: <VE1PR08MB51498685660361937A08D165980C0@VE1PR08MB5149.eurprd08.prod.outlook.com>

On Wed, Jan 22, 2020 at 10:36 AM Honnappa Nagarahalli
<Honnappa.Nagarahalli@arm.com> wrote:
>
> <snip>
>
> > Subject: [PATCH] event/dsw: use custom element size ring for control
> >
> > Replace DSW's use of regular DPDK rings (and code for packing/unpacking
> > control messages into void pointers) with custom size rings.
> >
> > In addition to cleaner code, this change allows DSW to support up to the
> > eventdev API's maximum of 255 ports by tweaking DSW_MAX_PORTS.
> >
> > Signed-off-by: Mattias Rönnblom <mattias.ronnblom@ericsson.com>

> > +
> > +# Depends on rte_ring_elem_*()
> > +allow_experimental_apis = true
> The rte_ring_elem_xxx API changes look good.
>
> Reviewed-by: Honnappa Nagarahalli <honnappa.nagarahalli@arm.com>

Applied to dpdk-next-eventdev/master. Thanks.


>
> > --
> > 2.17.1
>

      reply	other threads:[~2020-01-28  6:01 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-01-20 15:03 Mattias Rönnblom
2020-01-21 12:04 ` [dpdk-dev] [PATCH] event/dsw: use custom element size ring forcontrol Morten Brørup
2020-01-21 13:54   ` Mattias Rönnblom
2020-01-22  5:06 ` [dpdk-dev] [PATCH] event/dsw: use custom element size ring for control Honnappa Nagarahalli
2020-01-28  6:00   ` Jerin Jacob [this message]

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=CALBAE1PbsiXcXgkFv9EC1Hc3UTAJbUZ_q_htfnqmSG_cvvNvqQ@mail.gmail.com \
    --to=jerinjacobk@gmail.com \
    --cc=Honnappa.Nagarahalli@arm.com \
    --cc=dev@dpdk.org \
    --cc=jerinj@marvell.com \
    --cc=mattias.ronnblom@ericsson.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

DPDK patches and discussions

This inbox may be cloned and mirrored by anyone:

	git clone --mirror https://inbox.dpdk.org/dev/0 dev/git/0.git

	# If you have public-inbox 1.1+ installed, you may
	# initialize and index your mirror using the following commands:
	public-inbox-init -V2 dev dev/ https://inbox.dpdk.org/dev \
		dev@dpdk.org
	public-inbox-index dev

Example config snippet for mirrors.
Newsgroup available over NNTP:
	nntp://inbox.dpdk.org/inbox.dpdk.dev


AGPL code for this site: git clone https://public-inbox.org/public-inbox.git