From: Thomas Monjalon <thomas.monjalon@6wind.com>
To: John Daley <johndale@cisco.com>, adrien.mazarguil@6wind.com
Cc: dev@dpdk.org
Subject: Re: [PATCH 1/1] ethdev: don't consider device state when validating flows
Date: Thu, 06 Apr 2017 22:50:46 +0200 [thread overview]
Message-ID: <3201735.1C876yLKqy@xps13> (raw)
In-Reply-To: <20170324023659.28099-2-johndale@cisco.com>
Ping,
any progress on this patch?
2017-03-23 19:36, John Daley:
> PMDs only consider if a flow would be accepted or not the assuming the
> device had all it's resources available to it. Since state is not
> considered, -EEXIST and -EBUSY return codes no longer make sense and
> are removed. Also clarify the -ENOMEM has nothig to do with device
> resouces, only host resources needed rte_flow_validate().
>
> Signed-off-by: John Daley <johndale@cisco.com>
next prev parent reply other threads:[~2017-04-06 20:50 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-24 2:36 [PATCH 0/1] proposed minor change in rte_flow_validate semantics John Daley
2017-03-24 2:36 ` [PATCH 1/1] ethdev: don't consider device state when validating flows John Daley
2017-04-06 20:50 ` Thomas Monjalon [this message]
2017-04-06 22:41 ` [PATCH v2 0/1] fix flow validate comments John Daley
2017-04-06 22:41 ` [PATCH v2 1/1] ethdev: " John Daley
2017-04-07 0:23 ` [PATCH v3] " John Daley
2017-04-11 10:01 ` Adrien Mazarguil
2017-04-20 18:49 ` [PATCH v4] doc: " John Daley
2017-04-21 8:11 ` Adrien Mazarguil
2017-04-21 8:42 ` Thomas Monjalon
2017-03-24 9:46 ` [PATCH 0/1] proposed minor change in rte_flow_validate semantics Adrien Mazarguil
2017-03-24 17:23 ` John Daley (johndale)
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=3201735.1C876yLKqy@xps13 \
--to=thomas.monjalon@6wind.com \
--cc=adrien.mazarguil@6wind.com \
--cc=dev@dpdk.org \
--cc=johndale@cisco.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.