Eric Lee / smarc-fsl-linux-kernel

02 Mar, 2016

1 commit

  • 3a927bc7c   ovs: propagate per dp max headroom to all vports ... Browse Code »

    This patch implements bookkeeping support to compute the maximum
    headroom for all the devices in each datapath. When said value
    changes, the underlying devs are notified via the
    ndo_set_rx_headroom method.

    This also increases the internal vports xmit performance.

    Signed-off-by: Paolo Abeni
    Signed-off-by: David S. Miller

    Paolo Abeni
     

23 Oct, 2015

1 commit

  • fc4099f17   openvswitch: Fix egress tunnel info. ... Browse Code »

    While transitioning to netdev based vport we broke OVS
    feature which allows user to retrieve tunnel packet egress
    information for lwtunnel devices. Following patch fixes it
    by introducing ndo operation to get the tunnel egress info.
    Same ndo operation can be used for lwtunnel devices and compat
    ovs-tnl-vport devices. So after adding such device operation
    we can remove similar operation from ovs-vport.

    Fixes: 614732eaa12d ("openvswitch: Use regular VXLAN net_device device").
    Signed-off-by: Pravin B Shelar
    Signed-off-by: David S. Miller

    Pravin B Shelar
     

01 Sep, 2015

1 commit

  • 4c2227984   ip-tunnel: Use API to access tunnel metadata options. ... Browse Code »

    Currently tun-info options pointer is used in few cases to
    pass options around. But tunnel options can be accessed using
    ip_tunnel_info_opts() API without using the pointer. Following
    patch removes the redundant pointer and consistently make use
    of API.

    Signed-off-by: Pravin B Shelar
    Acked-by: Thomas Graf
    Reviewed-by: Jesse Gross
    Signed-off-by: David S. Miller

    Pravin B Shelar
     

30 Aug, 2015

2 commits

28 Aug, 2015

3 commits

  • c2ac66735   openvswitch: Allow matching on conntrack label ... Browse Code »

    Allow matching and setting the ct_label field. As with ct_mark, this is
    populated by executing the CT action. The label field may be modified by
    specifying a label and mask nested under the CT action. It is stored as
    metadata attached to the connection. Label modification occurs after
    lookup, and will only persist when the conntrack entry is committed by
    providing the COMMIT flag to the CT action. Labels are currently fixed
    to 128 bits in size.

    Signed-off-by: Joe Stringer
    Acked-by: Thomas Graf
    Acked-by: Pravin B Shelar
    Signed-off-by: David S. Miller

    Joe Stringer
     
  • 7f8a436ea   openvswitch: Add conntrack action ... Browse Code »

    Expose the kernel connection tracker via OVS. Userspace components can
    make use of the CT action to populate the connection state (ct_state)
    field for a flow. This state can be subsequently matched.

    Exposed connection states are OVS_CS_F_*:
    - NEW (0x01) - Beginning of a new connection.
    - ESTABLISHED (0x02) - Part of an existing connection.
    - RELATED (0x04) - Related to an established connection.
    - INVALID (0x20) - Could not track the connection for this packet.
    - REPLY_DIR (0x40) - This packet is in the reply direction for the flow.
    - TRACKED (0x80) - This packet has been sent through conntrack.

    When the CT action is executed by itself, it will send the packet
    through the connection tracker and populate the ct_state field with one
    or more of the connection state flags above. The CT action will always
    set the TRACKED bit.

    When the COMMIT flag is passed to the conntrack action, this specifies
    that information about the connection should be stored. This allows
    subsequent packets for the same (or related) connections to be
    correlated with this connection. Sending subsequent packets for the
    connection through conntrack allows the connection tracker to consider
    the packets as ESTABLISHED, RELATED, and/or REPLY_DIR.

    The CT action may optionally take a zone to track the flow within. This
    allows connections with the same 5-tuple to be kept logically separate
    from connections in other zones. If the zone is specified, then the
    "ct_zone" match field will be subsequently populated with the zone id.

    IP fragments are handled by transparently assembling them as part of the
    CT action. The maximum received unit (MRU) size is tracked so that
    refragmentation can occur during output.

    IP frag handling contributed by Andy Zhou.

    Based on original design by Justin Pettit.

    Signed-off-by: Joe Stringer
    Signed-off-by: Justin Pettit
    Signed-off-by: Andy Zhou
    Acked-by: Thomas Graf
    Acked-by: Pravin B Shelar
    Signed-off-by: David S. Miller

    Joe Stringer
     
  • be26b9a88   openvswitch: Move MASKED* macros to datapath.h ... Browse Code »

    This will allow the ovs-conntrack code to reuse these macros.

    Signed-off-by: Joe Stringer
    Acked-by: Thomas Graf
    Acked-by: Pravin B Shelar
    Signed-off-by: David S. Miller

    Joe Stringer
     

22 Jul, 2015

1 commit

  • 1d8fff907   ip_tunnel: Make ovs_tunnel_info and ovs_key_ipv4_tunnel generic ... Browse Code »

    Rename the tunnel metadata data structures currently internal to
    OVS and make them generic for use by all IP tunnels.

    Both structures are kernel internal and will stay that way. Their
    members are exposed to user space through individual Netlink
    attributes by OVS. It will therefore be possible to extend/modify
    these structures without affecting user ABI.

    Signed-off-by: Thomas Graf
    Signed-off-by: David S. Miller

    Thomas Graf
     

02 Jun, 2015

1 commit

  • ccea74457   openvswitch: include datapath actions with sampled-packet upcall to userspace ... Browse Code »

    If new optional attribute OVS_USERSPACE_ATTR_ACTIONS is added to an
    OVS_ACTION_ATTR_USERSPACE action, then include the datapath actions
    in the upcall.

    This Directly associates the sampled packet with the path it takes
    through the virtual switch. Path information currently includes mangling,
    encapsulation and decapsulation actions for tunneling protocols GRE,
    VXLAN, Geneve, MPLS and QinQ, but this extension requires no further
    changes to accommodate datapath actions that may be added in the
    future.

    Adding path information enhances visibility into complex virtual
    networks.

    Signed-off-by: Neil McKee
    Signed-off-by: David S. Miller

    Neil McKee
     

13 Mar, 2015

1 commit

  • 0c5c9fb55   net: Introduce possible_net_t ... Browse Code »

    Having to say
    > #ifdef CONFIG_NET_NS
    > struct net *net;
    > #endif

    in structures is a little bit wordy and a little bit error prone.

    Instead it is possible to say:
    > typedef struct {
    > #ifdef CONFIG_NET_NS
    > struct net *net;
    > #endif
    > } possible_net_t;

    And then in a header say:

    > possible_net_t net;

    Which is cleaner and easier to use and easier to test, as the
    possible_net_t is always there no matter what the compile options.

    Further this allows read_pnet and write_pnet to be functions in all
    cases which is better at catching typos.

    This change adds possible_net_t, updates the definitions of read_pnet
    and write_pnet, updates optional struct net * variables that
    write_pnet uses on to have the type possible_net_t, and finally fixes
    up the b0rked users of read_pnet and write_pnet.

    Signed-off-by: "Eric W. Biederman"
    Acked-by: Eric Dumazet
    Signed-off-by: David S. Miller

    Eric W. Biederman
     

10 Nov, 2014

4 commits

06 Nov, 2014

1 commit

06 Oct, 2014

1 commit

  • f0b128c1e   openvswitch: Wrap struct ovs_key_ipv4_tunnel in a new structure. ... Browse Code »

    Currently, the flow information that is matched for tunnels and
    the tunnel data passed around with packets is the same. However,
    as additional information is added this is not necessarily desirable,
    as in the case of pointers.

    This adds a new structure for tunnel metadata which currently contains
    only the existing struct. This change is purely internal to the kernel
    since the current OVS_KEY_ATTR_IPV4_TUNNEL is simply a compressed version
    of OVS_KEY_ATTR_TUNNEL that is translated at flow setup.

    Signed-off-by: Jesse Gross
    Signed-off-by: Andy Zhou
    Acked-by: Pravin B Shelar
    Signed-off-by: David S. Miller

    Jesse Gross
     

16 Sep, 2014

4 commits

  • 971427f35   openvswitch: Add recirc and hash action. ... Browse Code »

    Recirc action allows a packet to reenter openvswitch processing.
    currently openvswitch lookup flow for packet received and execute
    set of actions on that packet, with help of recirc action we can
    process/modify the packet and recirculate it back in openvswitch
    for another pass.

    OVS hash action calculates 5-tupple hash and set hash in flow-key
    hash. This can be used along with recirculation for distributing
    packets among different ports for bond devices.
    For example:
    OVS bonding can use following actions:
    Match on: bond flow; Action: hash, recirc(id)
    Match on: recirc-id == id and hash lower bits == a;
    Action: output port_bond_a

    Signed-off-by: Andy Zhou
    Acked-by: Jesse Gross
    Signed-off-by: Pravin B Shelar

    Andy Zhou
     
  • 8c8b1b83f   openvswitch: Use tun_key only for egress tunnel path. ... Browse Code »

    Currently tun_key is used for passing tunnel information
    on ingress and egress path, this cause confusion. Following
    patch removes its use on ingress path make it egress only parameter.

    Signed-off-by: Pravin B Shelar
    Acked-by: Andy Zhou

    Pravin B Shelar
     
  • 83c8df26a   openvswitch: refactor ovs flow extract API. ... Browse Code »

    OVS flow extract is called on packet receive or packet
    execute code path. Following patch defines separate API
    for extracting flow-key in packet execute code path.

    Signed-off-by: Pravin B Shelar
    Acked-by: Andy Zhou

    Pravin B Shelar
     
  • 2ff3e4e48   openvswitch: Remove pkt_key from OVS_CB ... Browse Code »

    OVS keeps pointer to packet key in skb->cb, but the packet key is
    store on stack. This could make code bit tricky. So it is better to
    get rid of the pointer.

    Signed-off-by: Pravin B Shelar

    Pravin B Shelar
     

31 Jul, 2014

1 commit

17 May, 2014

1 commit

15 Feb, 2014

1 commit

  • df9d9fdf8   openvswitch: rename ->sync to ->syncp ... Browse Code »

    Openvswitch defines u64_stats_sync as ->sync rather than ->syncp,
    so fails to compile with netdev_alloc_pcpu_stats(). So just rename it to ->syncp.

    Reported-by: kbuild test robot
    Fixes: 1c213bd24ad04f4430031 (net: introduce netdev_alloc_pcpu_stats() for drivers)
    Cc: David S. Miller
    Signed-off-by: Cong Wang
    Reviewed-by: Flavio Leitner
    Signed-off-by: David S. Miller

    WANG Cong
     

07 Jan, 2014

3 commits

20 Nov, 2013

1 commit

23 Oct, 2013

1 commit

04 Oct, 2013

2 commits

18 Sep, 2013

1 commit

24 Aug, 2013

1 commit

  • 03f0d916a   openvswitch: Mega flow implementation ... Browse Code »

    Add wildcarded flow support in kernel datapath.

    Wildcarded flow can improve OVS flow set up performance by avoid sending
    matching new flows to the user space program. The exact performance boost
    will largely dependent on wildcarded flow hit rate.

    In case all new flows hits wildcard flows, the flow set up rate is
    within 5% of that of linux bridge module.

    Pravin has made significant contributions to this patch. Including API
    clean ups and bug fixes.

    Signed-off-by: Pravin B Shelar
    Signed-off-by: Andy Zhou
    Signed-off-by: Jesse Gross

    Andy Zhou
     

20 Jun, 2013

2 commits

16 Apr, 2013

1 commit

  • 8e4e1713e   openvswitch: Simplify datapath locking. ... Browse Code »

    Currently OVS uses combination of genl and rtnl lock to protect
    datapath state. This was done due to networking stack locking.
    But this has complicated locking and there are few lock ordering
    issues with new tunneling protocols.
    Following patch simplifies locking by introducing new ovs mutex
    and now this lock is used to protect entire ovs state.

    Signed-off-by: Pravin B Shelar
    Signed-off-by: Jesse Gross

    Pravin B Shelar
     

11 Apr, 2013

1 commit

23 Feb, 2013

1 commit

  • 4490108b4   openvswitch: Allow OVS_USERSPACE_ATTR_USERDATA to be variable length. ... Browse Code »

    Until now, the optional OVS_USERSPACE_ATTR_USERDATA attribute had to be
    exactly 64 bits long, if it was present. However, 64 bits is not enough
    space to associate as much information with a flow as would be convenient
    for some userspace features now under development. This commit generalizes
    the attribute, allowing it to be any length.

    This generalization is backward-compatible: if userspace only uses 64-bit
    attributes, then it will not see any change in behavior.

    CC: Romain Lenglet
    Signed-off-by: Ben Pfaff
    Signed-off-by: Jesse Gross

    Ben Pfaff
     

11 Sep, 2012

1 commit

  • 15e473046   netlink: Rename pid to portid to avoid confusion ... Browse Code »

    It is a frequent mistake to confuse the netlink port identifier with a
    process identifier. Try to reduce this confusion by renaming fields
    that hold port identifiers portid instead of pid.

    I have carefully avoided changing the structures exported to
    userspace to avoid changing the userspace API.

    I have successfully built an allyesconfig kernel with this change.

    Signed-off-by: "Eric W. Biederman"
    Acked-by: Stephen Hemminger
    Signed-off-by: David S. Miller

    Eric W. Biederman
     

04 Sep, 2012

1 commit