DPDK patches and discussions
 help / color / mirror / Atom feed
From: Stephen Hemminger <stephen@networkplumber.org>
To: Thomas Monjalon <thomas@monjalon.net>
Cc: dev@dpdk.org, david.marchand@redhat.com, aconole@redhat.com,
	joyce.kong@arm.com
Subject: Re: [dpdk-dev] [PATCH] test: add missing ticketlock test to fast tests
Date: Sun, 17 Jan 2021 10:11:24 -0800	[thread overview]
Message-ID: <20210117101124.651e401c@hermes.local> (raw)
In-Reply-To: <8253139.bqY7tb8vIG@thomas>

On Sun, 17 Jan 2021 18:57:56 +0100
Thomas Monjalon <thomas@monjalon.net> wrote:

> 14/01/2021 17:58, Stephen Hemminger:
> > The ticketlock test is fast and should be run all the time.  
> 
> I think it was not added because it includes a perf test.
> Cc'ing more people for comments.
> 
> 

Other lock code (rwlock is very similar and in the fast tests).

  reply	other threads:[~2021-01-17 18:11 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-01-14 16:58 Stephen Hemminger
2021-01-17 17:57 ` Thomas Monjalon
2021-01-17 18:11   ` Stephen Hemminger [this message]
2021-01-18 13:29     ` Aaron Conole
2021-01-19 10:47       ` Thomas Monjalon

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=20210117101124.651e401c@hermes.local \
    --to=stephen@networkplumber.org \
    --cc=aconole@redhat.com \
    --cc=david.marchand@redhat.com \
    --cc=dev@dpdk.org \
    --cc=joyce.kong@arm.com \
    --cc=thomas@monjalon.net \
    /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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).