xen-netback: better names for thresholds
authorWei Liu <wei.liu2@citrix.com>
Thu, 2 May 2013 00:43:59 +0000 (00:43 +0000)
committerDavid S. Miller <davem@davemloft.net>
Thu, 2 May 2013 20:50:08 +0000 (16:50 -0400)
commit376414945d15aa636e65f7e773c1e398b7a21cb9
tree4950ccac38966156f0a5bee6665efd666be610f1
parent59ccb4ebbc35e36a3c143f2d1355deb75c2e628f
xen-netback: better names for thresholds

This patch only changes some names to avoid confusion.

In this patch we have:

  MAX_SKB_SLOTS_DEFAULT -> FATAL_SKB_SLOTS_DEFAULT
  max_skb_slots -> fatal_skb_slots
  #define XEN_NETBK_LEGACY_SLOTS_MAX XEN_NETIF_NR_SLOTS_MIN

The fatal_skb_slots is the threshold to determine whether a packet is
malicious.

XEN_NETBK_LEGACY_SLOTS_MAX is the maximum slots a valid packet can have at
this point. It is defined to be XEN_NETIF_NR_SLOTS_MIN because that's
guaranteed to be supported by all backends.

Suggested-by: Ian Campbell <ian.campbell@citrix.com>
Signed-off-by: Wei Liu <wei.liu2@citrix.com>
Signed-off-by: David S. Miller <davem@davemloft.net>
drivers/net/xen-netback/netback.c