From: Stephen Hemminger <stephen@networkplumber.org>
To: Simon Horman <simon.horman@netronome.com>
Cc: dev@openvswitch.org, netdev@vger.kernel.org,
Pravin Shelar <pshelar@nicira.com>,
Jesse Gross <jesse@nicira.com>, Jiri Pirko <jiri@resnulli.us>,
Thomas Graf <tgraf@suug.ch>,
John Fastabend <john.r.fastabend@intel.com>,
Scott Feldman <sfeldma@gmail.com>,
Roopa Prabhu <roopa@cumulusnetworks.com>,
Alexi Starovoitov <alexei.starovoitov@gmail.com>,
Florian Fainelli <f.fainelli@gmail.com>,
Jamal Hadi Salim <jhs@mojatatu.com>,
Bert van Leeuwen <bert.vanleeuwen@netronome.com>
Subject: Re: [PATCH/RFC] datapath: offload hooks
Date: Tue, 7 Oct 2014 21:50:36 -0700 [thread overview]
Message-ID: <20141007215036.65f1d439@urahara> (raw)
In-Reply-To: <1412728851-32534-1-git-send-email-simon.horman@netronome.com>
On Wed, 8 Oct 2014 09:40:51 +0900
Simon Horman <simon.horman@netronome.com> wrote:
> +struct ovs_offload_ops {
> + /* Flow offload functions */
> + /* Called when a flow entry is added to the flow table */
> + void (*flow_new)(struct sw_flow *);
> + /* Called when a flow entry is modified */
> + void (*flow_set)(struct sw_flow *);
> + /* Called when a flow entry is removed from the flow table */
> + void (*flow_del)(struct sw_flow *);
> + /* Called when flow stats are queried */
> + void (*flow_stats_get)(const struct sw_flow *, struct ovs_flow_stats *,
> + unsigned long *used, __be16 *tcp_flags);
> + /* Called when flow stats are removed */
> + void (*flow_stats_clear)(struct sw_flow *);
> +
> + /* Port offload functions */
> + /* Called when a vport is added to the datapath */
> + void (*vport_new)(struct sk_buff *, struct vport *,
> + struct vport_parms *);
> + /* Called when a vport is modified */
> + void (*vport_set)(struct sk_buff *, struct vport *);
> + /* Called when a vport is removed from the datapath */
> + void (*vport_del)(struct sk_buff *, struct vport *);
> + /* Called when vport stats are queried */
> + void (*vport_stats_get)(struct vport *, struct ovs_vport_stats *);
> + /* Called when vport stats are set */
> + void (*vport_stats_set)(struct vport *, struct ovs_vport_stats *);
> +
> + /* Datapath offload functions */
> + /* Called when the datapath is created */
> + void (*dp_new)(struct datapath *);
> + /* Called when the datapath is modified */
> + void (*dp_set)(struct datapath *);
> + /* Called when the datapath is removed */
> + void (*dp_del)(struct datapath *);
> + /* Called when the datapath stats are queried */
> + void (*dp_stats_get)(struct datapath *, struct ovs_dp_stats *);
> +}
For security, you should mark any ops type table const, so an
attacker can't find a home to poke their favorite routine into.
next prev parent reply other threads:[~2014-10-08 4:50 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-10-08 0:40 [PATCH/RFC] datapath: offload hooks Simon Horman
2014-10-08 4:50 ` Stephen Hemminger [this message]
2014-10-08 23:51 ` Simon Horman
2014-10-08 4:55 ` Stephen Hemminger
2014-10-09 0:07 ` Simon Horman
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=20141007215036.65f1d439@urahara \
--to=stephen@networkplumber.org \
--cc=alexei.starovoitov@gmail.com \
--cc=bert.vanleeuwen@netronome.com \
--cc=dev@openvswitch.org \
--cc=f.fainelli@gmail.com \
--cc=jesse@nicira.com \
--cc=jhs@mojatatu.com \
--cc=jiri@resnulli.us \
--cc=john.r.fastabend@intel.com \
--cc=netdev@vger.kernel.org \
--cc=pshelar@nicira.com \
--cc=roopa@cumulusnetworks.com \
--cc=sfeldma@gmail.com \
--cc=simon.horman@netronome.com \
--cc=tgraf@suug.ch \
/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).