From: Thomas Monjalon <thomas@monjalon.net>
To: Jerin Jacob <jerin.jacob@caviumnetworks.com>
Cc: dev@dpdk.org, Hemant Agrawal <hemant.agrawal@nxp.com>,
john.mcnamara@intel.com
Subject: Re: [PATCH v3 ] ethdev: introduce lock-free txq capability flag
Date: Tue, 18 Jul 2017 16:43:55 +0300 [thread overview]
Message-ID: <13765612.oLuGorxqyg@xps> (raw)
In-Reply-To: <ff0cb451-8a6b-efb2-bd60-07fb9c2224ca@nxp.com>
13/07/2017 15:02, Hemant Agrawal:
> On 7/10/2017 10:29 PM, Jerin Jacob wrote:
> > Introducing the DEV_TX_OFFLOAD_MT_LOCKFREE TX capability flag.
> > if a PMD advertises DEV_TX_OFFLOAD_MT_LOCKFREE capable, multiple threads
> > can invoke rte_eth_tx_burst() concurrently on the same tx queue without
> > SW lock. This PMD feature will be useful in the following use cases and
> > found in the OCTEON family of NPUs.
> >
> > 1) Remove explicit spinlock in some applications where lcores
> > to TX queues are not mapped 1:1.
> > example: OVS has such instance
> > https://github.com/openvswitch/ovs/blob/master/lib/netdev-dpdk.c#L299
> > https://github.com/openvswitch/ovs/blob/master/lib/netdev-dpdk.c#L1859
> > See the the usage of tx_lock spinlock.
> >
> > 2) In the eventdev use case, avoid dedicating a separate TX core for
> > transmitting and thus enables more scaling as all workers can
> > send the packets.
> >
> > Signed-off-by: Jerin Jacob <jerin.jacob@caviumnetworks.com>
>
> You may also like to add this capability in "doc/guides/nics/features/*.ini"
I've just added the feature "Lock-free Tx queue" in features/default.ini.
> Acked-by: Hemant Agrawal <hemant.agrawal@nxp.com>
Applied, thanks
next prev parent reply other threads:[~2017-07-18 13:43 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-04-21 12:22 [PATCH] ethdev: add lock-less txq capability flag Jerin Jacob
2017-04-24 12:34 ` Thomas Monjalon
2017-04-27 11:00 ` Jerin Jacob
2017-07-05 17:46 ` Thomas Monjalon
2017-07-06 6:00 ` Jerin Jacob
2017-07-06 6:21 ` [PATCH v2] ethdev: introduce lock-free " Jerin Jacob
2017-07-08 16:08 ` Thomas Monjalon
2017-07-10 16:56 ` Jerin Jacob
2017-07-10 16:59 ` [PATCH v3 ] " Jerin Jacob
2017-07-13 12:02 ` Hemant Agrawal
2017-07-18 13:43 ` Thomas Monjalon [this message]
2017-07-13 18:42 ` santosh
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=13765612.oLuGorxqyg@xps \
--to=thomas@monjalon.net \
--cc=dev@dpdk.org \
--cc=hemant.agrawal@nxp.com \
--cc=jerin.jacob@caviumnetworks.com \
--cc=john.mcnamara@intel.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.