DPDK patches and discussions
 help / color / mirror / Atom feed
From: "Iremonger, Bernard" <bernard.iremonger@intel.com>
To: "Ananyev, Konstantin" <konstantin.ananyev@intel.com>,
	"dev@dpdk.org" <dev@dpdk.org>
Subject: Re: [dpdk-dev] [PATCH] test/ipsec: fix test suite setup function
Date: Thu, 17 Jan 2019 11:12:36 +0000	[thread overview]
Message-ID: <8CEF83825BEC744B83065625E567D7C260D4F8B3@IRSMSX108.ger.corp.intel.com> (raw)
In-Reply-To: <2601191342CEEE43887BDE71AB977258010D904F1F@irsmsx105.ger.corp.intel.com>

Hi Konstantin,

<snip>

> > > > > I think you need to check driver capabilities, instead of
> > > > > relying on driver
> > > name.
> > > >
> > > > I don't think it is necessary to check the driver capabilities.
> > >
> > > I still think that the valid way to check supported algorithms is to
> > > check device capabilities, not the driver name.
> >
> > In the testsuite_setup() function the parameters for the
> > check_cryptodev_capability() are not setup. They are setup in the test
> functions of the testsuite.
> 
> Ok, so what prevents us to setup them earlier?

This will require some refactoring of the tests, I will investigate.

<snip>

> > As discussed offline it should be sufficient to test with the crypto_dev NULL
> PMD.
> 
> As we discussed  offline - yes, I don't think it's too excessive to verify
> ipsec_autotest with each existing driver that supports _NULL algs, but I don't
> see the reason why it shouldn't support anything except crypto_null.
> Konstantin

Ok, I will investigate what needs to be done.

Regards,

Bernard.

  reply	other threads:[~2019-01-17 11:12 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-01-15 11:19 Bernard Iremonger
2019-01-15 11:55 ` Ananyev, Konstantin
2019-01-15 12:34   ` Iremonger, Bernard
2019-01-15 12:49     ` Ananyev, Konstantin
2019-01-17 10:04       ` Iremonger, Bernard
2019-01-17 10:30         ` Ananyev, Konstantin
2019-01-17 11:12           ` Iremonger, Bernard [this message]
2019-01-17 10:15 ` [dpdk-dev] [PATCH v2] " Bernard Iremonger
2019-01-17 10:34   ` Ananyev, Konstantin
2019-01-17 11:20     ` Iremonger, Bernard
2019-01-17 15:35       ` Iremonger, Bernard
2019-01-17 16:03   ` [dpdk-dev] [PATCH v3] " Bernard Iremonger
2019-01-17 17:05     ` Ananyev, Konstantin
2019-01-17 23:30       ` 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=8CEF83825BEC744B83065625E567D7C260D4F8B3@IRSMSX108.ger.corp.intel.com \
    --to=bernard.iremonger@intel.com \
    --cc=dev@dpdk.org \
    --cc=konstantin.ananyev@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 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).