From: ohilyard@iol.unh.edu
To: dev@dpdk.org
Cc: Honnappa.Nagarahalli@arm.com, thomas@monjalon.net,
Owen Hilyard <ohilyard@iol.unh.edu>
Subject: [PATCH v1 3/4] app/test-pmd-api: Add protobuf file
Date: Thu, 7 Apr 2022 17:47:07 -0400 [thread overview]
Message-ID: <20220407214707.29730-4-ohilyard@iol.unh.edu> (raw)
In-Reply-To: <20220407214707.29730-1-ohilyard@iol.unh.edu>
From: Owen Hilyard <ohilyard@iol.unh.edu>
This file contains the gRPC definitions for the api as it currently
stands.
Signed-off-by: Owen Hilyard <ohilyard@iol.unh.edu>
---
app/test-pmd-api/api.proto | 12 ++++++++++++
1 file changed, 12 insertions(+)
create mode 100644 app/test-pmd-api/api.proto
diff --git a/app/test-pmd-api/api.proto b/app/test-pmd-api/api.proto
new file mode 100644
index 0000000000..ba52e379e9
--- /dev/null
+++ b/app/test-pmd-api/api.proto
@@ -0,0 +1,12 @@
+syntax = "proto3";
+import "google/protobuf/empty.proto";
+
+message AclSetupArgs {
+ repeated string args = 1;
+}
+
+service TestpmdAPI {
+ rpc acl_setup (AclSetupArgs) returns (google.protobuf.Empty);
+ rpc acl_search (google.protobuf.Empty) returns (google.protobuf.Empty);
+ rpc acl_cleanup_config (google.protobuf.Empty) returns (google.protobuf.Empty);
+}
\ No newline at end of file
--
2.30.2
next prev parent reply other threads:[~2022-04-07 21:47 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-07 21:47 [PATCH v1 0/4] [RFC] Testpmd RPC API ohilyard
2022-04-07 21:47 ` [PATCH v1 1/4] app/test-pmd-api: Add C++ Compiler ohilyard
2023-10-02 18:33 ` Stephen Hemminger
2022-04-07 21:47 ` [PATCH v1 2/4] app/test-pmd-api: Add POC with gRPC deps ohilyard
2022-04-07 21:47 ` ohilyard [this message]
2022-04-07 21:47 ` [PATCH v1 4/4] app/test-pmd-api: Implementation files for the API ohilyard
2022-04-11 14:27 ` [PATCH v1 0/4] [RFC] Testpmd RPC API Jerin Jacob
2022-04-11 17:48 ` Owen Hilyard
2022-04-12 6:07 ` Jerin Jacob
2022-04-13 12:47 ` Owen Hilyard
2022-04-14 12:07 ` Ananyev, Konstantin
2022-04-14 20:09 ` Owen Hilyard
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=20220407214707.29730-4-ohilyard@iol.unh.edu \
--to=ohilyard@iol.unh.edu \
--cc=Honnappa.Nagarahalli@arm.com \
--cc=dev@dpdk.org \
--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).