Hi Jiannan,
On Fri, Jul 14, 2017 at 01:01:34AM +, Jiannan Ouyang wrote:
> > you're unconditionally binding to both GTP0 and GTP1 UDP ports. This is
> > done selectively based on netlink attributes in the existing "normal"
> > non-OVS kernel code, i.e. the control is left to the user.
> >
> >
Hi Harald,
> On 7/13/17, 12:35 AM, "Harald Welte" wrote:
>
> > +static int gtp_dev_open(struct net_device *dev)
> > +{
> > + struct gtp_dev *gtp = netdev_priv(dev);
> > + struct net *net = gtp->net;
> > + struct socket *sock1u;
> > + struct socket *sock0;
> > + struct udp_tunnel_sock_c
On 12 July 2017 at 17:44, Jiannan Ouyang wrote:
> Add the gtp_create_flow_based_dev() interface to create flow-based gtp
> net_device, which sets gtp->collect_md. Under flow-based mode, UDP sockets are
> created and maintained in kernel.
>
> Signed-off-by: Jiannan Ouyang
> ---
> +static int gt
Hi Jiannan,
please keep in mind I have zero clue about OVS, so I cannot really
comment on what is customary in that context and what not. However,
some general review from the GTP point of view below:
On Wed, Jul 12, 2017 at 05:44:54PM -0700, Jiannan Ouyang wrote:
> Add the gtp_create_flow_based
Add the gtp_create_flow_based_dev() interface to create flow-based gtp
net_device, which sets gtp->collect_md. Under flow-based mode, UDP sockets are
created and maintained in kernel.
Signed-off-by: Jiannan Ouyang
---
drivers/net/gtp.c | 213 +-
