DPDK patches and discussions
 help / color / mirror / Atom feed
From: Thomas Monjalon <thomas@monjalon.net>
To: Stephen Hemminger <stephen@networkplumber.org>
Cc: dev@dpdk.org, david.marchand@redhat.com, joyce.kong@arm.com,
	Aaron Conole <aconole@redhat.com>
Subject: Re: [dpdk-dev] [PATCH] test: add missing ticketlock test to fast tests
Date: Tue, 19 Jan 2021 11:47:01 +0100	[thread overview]
Message-ID: <5708965.ZrF6TBJDgr@thomas> (raw)
In-Reply-To: <f7th7newezm.fsf@dhcp-25.97.bos.redhat.com>

18/01/2021 14:29, Aaron Conole:
> Stephen Hemminger <stephen@networkplumber.org> writes:
> 
> > 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).
> 
> I agree, it should be included.  I did some digging and seems it wasn't
> ever part of this set of lists, but could have been all along.  As for
> execution time, here's a run from the 0-day bot:
> 
> https://github.com/ovsrobot/dpdk/actions/runs/486047432
> 
> 17m seems to be in the normal range.
> 
> Acked-by: Aaron Conole <aconole@redhat.com>
> 
> Thanks, Stephen!

Applied, thanks




      reply	other threads:[~2021-01-19 10:47 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
2021-01-18 13:29     ` Aaron Conole
2021-01-19 10:47       ` Thomas Monjalon [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=5708965.ZrF6TBJDgr@thomas \
    --to=thomas@monjalon.net \
    --cc=aconole@redhat.com \
    --cc=david.marchand@redhat.com \
    --cc=dev@dpdk.org \
    --cc=joyce.kong@arm.com \
    --cc=stephen@networkplumber.org \
    /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).