From: David Marchand <david.marchand@redhat.com>
To: Andrew Rybchenko <andrew.rybchenko@oktetlabs.ru>
Cc: Thomas Monjalon <thomas@monjalon.net>,
Ivan Malov <ivan.malov@oktetlabs.ru>, dev <dev@dpdk.org>,
Ferruh Yigit <ferruh.yigit@intel.com>,
Ori Kam <orika@nvidia.com>
Subject: Re: [dpdk-dev] [PATCH] ethdev: fine tune error reporting in pick transfer proxy API
Date: Tue, 2 Nov 2021 18:04:23 +0100 [thread overview]
Message-ID: <CAJFAV8yPMCR-ax=1BiiYeuMwCxhAG5YWc8hQ6mYu+41vVhpQHw@mail.gmail.com> (raw)
In-Reply-To: <4cf45c3f-47df-b6c9-7f9e-2ce996878e45@oktetlabs.ru>
On Tue, Nov 2, 2021 at 4:59 PM Andrew Rybchenko
<andrew.rybchenko@oktetlabs.ru> wrote:
> >> IMHO, spamming of testpmd logs in described case should be fixed
> >> in testpmd itself to avoid logs in the case of ENOTSUP. That's it.
> >
> > I think we should not call this API in testpmd
> > if not doing rte_flow transfer rule.
> >
>
> Since testpmd does not pursue top flow insertion rate etc,
> I tend to agree. For debugging purposes (testpmd main goal)
> the best way is to pick proxy just before usage without any
> caching etc.
+1.
--
David Marchand
next prev parent reply other threads:[~2021-11-02 17:04 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-10-27 9:00 Ivan Malov
2021-10-27 9:46 ` Thomas Monjalon
2021-10-27 9:55 ` Ivan Malov
2021-10-27 10:57 ` Thomas Monjalon
2021-10-28 16:24 ` Ivan Malov
2021-10-29 8:11 ` Thomas Monjalon
2021-11-01 9:41 ` Andrew Rybchenko
2021-11-02 15:45 ` Thomas Monjalon
2021-11-02 15:58 ` Andrew Rybchenko
2021-11-02 17:04 ` David Marchand [this message]
2021-11-10 14:21 ` Ferruh Yigit
2021-11-15 14:15 ` Ivan Malov
2021-11-15 15:09 ` Thomas Monjalon
2021-11-15 15:30 ` Ori Kam
2021-11-03 14:38 ` Ori Kam
2021-11-16 15:38 ` [PATCH] app/testpmd: fix flow transfer proxy port handling Ivan Malov
2021-11-16 19:23 ` Ori Kam
2021-11-17 7:41 ` Slava Ovsiienko
2021-11-17 10:54 ` Ferruh Yigit
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='CAJFAV8yPMCR-ax=1BiiYeuMwCxhAG5YWc8hQ6mYu+41vVhpQHw@mail.gmail.com' \
--to=david.marchand@redhat.com \
--cc=andrew.rybchenko@oktetlabs.ru \
--cc=dev@dpdk.org \
--cc=ferruh.yigit@intel.com \
--cc=ivan.malov@oktetlabs.ru \
--cc=orika@nvidia.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).