Skip to contentSkip to conversation

net/core/ethtool: New Commands to Configure IOV features

RFC PATCH In review Greg Rose 2 participants 4 messages Sep 22, 2011 – Oct 13, 2011

Subsystems (4)
Networking Network drivers Intel Ethernet Networking ethtool
lore
Share & tools
lore

Greg Rose

author
#0 lore raw

RFC PATCH v2 1/2 net/core/ethtool: New Commands to Configure IOV features

The only currently supported method of configuring the number of VFs is through the max_vfs module parameter. This method is inadequate to support scenarios in which the user might wish to have varying numbers of VFs per PF. There is additional support for drivers that want to partition some driver resources to additional net devices and for configuring the number of Tx/Rx queue pairs per VF.

Signed-off-by Greg Rose <[email protected]>

---

 include/linux/ethtool.h |   30 +++++++++++++++++++++++++++++-
 net/core/ethtool.c      |   38 ++++++++++++++++++++++++++++++++++++++
 2 files changed, 67 insertions(+), 1 deletions(-)
include/linux/ethtool.h +29 -1
index 45f00b6..448730f 100644
@@ -720,6 +720,27 @@ enum ethtool_sfeatures_retval_bits {
 #define ETHTOOL_F_WISH          (1 << ETHTOOL_F_WISH__BIT)
 #define ETHTOOL_F_COMPAT        (1 << ETHTOOL_F_COMPAT__BIT)
 
+enum ethtool_iov_modes {
+	ETHTOOL_IOV_MODE_NONE,
+	ETHTOOL_IOV_MODE_SRIOV,
+	ETHTOOL_IOV_MODE_NETDEVS,
+};
+
+#define	ETHTOOL_IOV_CMD_CONFIGURE_SRIOV		1
+#define	ETHTOOL_IOV_CMD_CONFIGURE_NETDEVS	2
+#define	ETHTOOL_IOV_CMD_CONFIGURE_VF_QUEUES	3
+
+struct ethtool_iov_set_cmd {
+	__u32 cmd;
+	__u32 set_cmd;
+	__u32 cmd_param;
+};
+
+struct ethtool_iov_get_cmd {
+	__u32 cmd;
+	__u32 mode;
+};
+
 #ifdef __KERNEL__
 
 #include <linux/rculist.h>

@@ -879,6 +900,8 @@ bool ethtool_invalid_flags(struct net_device *dev, u32 data, u32 supported);
  * 		   and flag of the device.
  * @get_dump_data: Get dump data.
  * @set_dump: Set dump specific flags to the device.
+ * @iov_set_cmd: Set IOV parameters - number of VFs or VM Queues
+ * @iov_get_cmd: Get current IOV parameters and configuration
  *
  * All operations are optional (i.e. the function pointer may be set
  * to %NULL) and callers must take this into account.  Callers must

@@ -956,7 +979,10 @@ struct ethtool_ops {
 	int	(*get_dump_data)(struct net_device *,
 				 struct ethtool_dump *, void *);
 	int	(*set_dump)(struct net_device *, struct ethtool_dump *);
-
+	int	(*iov_set_cmd)(struct net_device *,
+			struct ethtool_iov_set_cmd *);
+	int	(*iov_get_cmd)(struct net_device *,
+			struct ethtool_iov_get_cmd *);
 };
 #endif /* __KERNEL__ */
 

@@ -1030,6 +1056,8 @@ struct ethtool_ops {
 #define ETHTOOL_SET_DUMP	0x0000003e /* Set dump settings */
 #define ETHTOOL_GET_DUMP_FLAG	0x0000003f /* Get dump settings */
 #define ETHTOOL_GET_DUMP_DATA	0x00000040 /* Get dump data */
+#define ETHTOOL_IOV_SET_CMD	0x00000041 /* Set IOV parameters */
+#define ETHTOOL_IOV_GET_CMD	0x00000042 /* Get IOV parameters */
 
 /* compatibility with older code */
 #define SPARC_ETH_GSET		ETHTOOL_GSET
net/core/ethtool.c +38 -0
index f444817..a469e40 100644
@@ -1633,6 +1633,38 @@ out:
 	return ret;
 }
 
+static int ethtool_iov_set_command(struct net_device *dev,
+				  void __user *useraddr)
+{
+	struct ethtool_iov_set_cmd iov_cmd;
+
+	if (!dev->ethtool_ops->iov_set_cmd)
+		return -EOPNOTSUPP;
+	if (copy_from_user(&iov_cmd, useraddr, sizeof(iov_cmd)))
+		return -EFAULT;
+
+	return dev->ethtool_ops->iov_set_cmd(dev, &iov_cmd);
+}
+
+static int ethtool_iov_get_command(struct net_device *dev,
+				  void __user *useraddr)
+{
+	int ret;
+	struct ethtool_iov_get_cmd iov_cmd;
+
+	if (!dev->ethtool_ops->iov_get_cmd)
+		return -EOPNOTSUPP;
+	if (copy_from_user(&iov_cmd, useraddr, sizeof(iov_cmd)))
+		return -EFAULT;
+
+	ret = dev->ethtool_ops->iov_get_cmd(dev, &iov_cmd);
+	if (!ret)
+		ret = copy_to_user(useraddr, &iov_cmd, sizeof(iov_cmd));
+
+	return ret;
+}
+
+
 /* The main entry point in this file.  Called from net/core/dev.c */
 
 int dev_ethtool(struct net *net, struct ifreq *ifr)

@@ -1855,6 +1887,12 @@ int dev_ethtool(struct net *net, struct ifreq *ifr)
 	case ETHTOOL_GET_DUMP_DATA:
 		rc = ethtool_get_dump_data(dev, useraddr);
 		break;
+	case ETHTOOL_IOV_SET_CMD:
+		rc = ethtool_iov_set_command(dev, useraddr);
+		break;
+	case ETHTOOL_IOV_GET_CMD:
+		rc = ethtool_iov_get_command(dev, useraddr);
+		break;
 	default:
 		rc = -EOPNOTSUPP;
 	}
author
#1 lore raw

RFC PATCH v2 2/2 ixgbe: Add support for new ethtool IOV configuration commands

Implement driver support for the new ethtool command to configure the number of VFs per PF independently. The framework is in place for support of two other features that allow the user to partition some of the I/O resources of the device to additional semi-independent net devices and to set the number of queues per VF.

Signed-off-by Greg Rose <[email protected]>

---

 drivers/net/ethernet/intel/ixgbe/ixgbe.h         |    1 
 drivers/net/ethernet/intel/ixgbe/ixgbe_ethtool.c |  110 ++++++++++++++++++++++
 drivers/net/ethernet/intel/ixgbe/ixgbe_main.c    |    3 +
 3 files changed, 113 insertions(+), 1 deletions(-)
drivers/net/ethernet/intel/ixgbe/ixgbe.h +1 -0
index 8fab322..cea2323 100644
@@ -528,6 +528,7 @@ struct ixgbe_adapter {
 	int fdir_filter_count;
 	u32 timer_event_accumulator;
 	u32 vferr_refcount;
+	const struct ixgbe_info *saved_ii;
 };
 
 struct ixgbe_fdir_filter {
drivers/net/ethernet/intel/ixgbe/ixgbe_ethtool.c +109 -1

128 lines not on this page · raw message

drivers/net/ethernet/intel/ixgbe/ixgbe_main.c +3 -0
index 99ff8b2..546f3ba 100644
@@ -7591,6 +7591,9 @@ static void __devinit ixgbe_probe_vf(struct ixgbe_adapter *adapter,
 	if (hw->mac.type == ixgbe_mac_82598EB)
 		return;
 
+	/* need to save this away in case SR-IOV is reconfigured */
+	adapter->saved_ii = ii;
+
 	/* The 82599 supports up to 64 VFs per physical function
 	 * but this implementation limits allocation to 63 so that
 	 * basic networking resources are still available to the
#2 lore raw
In reply to Greg Rose
Quoted 27 lines · Greg Rose

The only currently supported method of configuring the number of VFs is through the max_vfs module parameter. This method is inadequate to support scenarios in which the user might wish to have varying numbers of VFs per PF. There is additional support for drivers that want to partition some driver resources to additional net devices and for configuring the number of Tx/Rx queue pairs per VF.

Signed-off-by Greg Rose <[email protected]>

---

 include/linux/ethtool.h |   30 +++++++++++++++++++++++++++++-
 net/core/ethtool.c      |   38 ++++++++++++++++++++++++++++++++++++++
 2 files changed, 67 insertions(+), 1 deletions(-)
include/linux/ethtool.h +5 -0
index 45f00b6..448730f 100644
@@ -720,6 +720,27 @@ enum ethtool_sfeatures_retval_bits {
 #define ETHTOOL_F_WISH          (1 << ETHTOOL_F_WISH__BIT)
 #define ETHTOOL_F_COMPAT        (1 << ETHTOOL_F_COMPAT__BIT)
 
+enum ethtool_iov_modes {
+	ETHTOOL_IOV_MODE_NONE,
+	ETHTOOL_IOV_MODE_SRIOV,
+	ETHTOOL_IOV_MODE_NETDEVS,
+};

include/linux/ethtool.h enum ethtool_sfeatures_retval_bits { · line 737

Quoted 10 lines
include/linux/ethtool.h +10 -0
+
+#define	ETHTOOL_IOV_CMD_CONFIGURE_SRIOV		1
+#define	ETHTOOL_IOV_CMD_CONFIGURE_NETDEVS	2
+#define	ETHTOOL_IOV_CMD_CONFIGURE_VF_QUEUES	3
+
+struct ethtool_iov_set_cmd {
+	__u32 cmd;
+	__u32 set_cmd;
+	__u32 cmd_param;
+};

Why introduce sub-commands?

include/linux/ethtool.h enum ethtool_sfeatures_retval_bits { · line 742

Quoted 4 lines
include/linux/ethtool.h +4 -0
+struct ethtool_iov_get_cmd {
+	__u32 cmd;
+	__u32 mode;
+};

Why is it only possible to get the mode?

It really seems to make more sense to group these three parameters together and get/set them all at once. But if you can justify making them separate then struct ethtool_value is the type to use.

In any case, any new types or macros need comments.

[...]

Quoted 4 lines
include/linux/ethtool.h +4 -0
+static int ethtool_iov_get_command(struct net_device *dev,
+				  void __user *useraddr)
+{
+	int ret;

include/linux/ethtool.h enum ethtool_sfeatures_retval_bits {

Quoted 10 lines
include/linux/ethtool.h +10 -0
+	struct ethtool_iov_get_cmd iov_cmd;
+
+	if (!dev->ethtool_ops->iov_get_cmd)
+		return -EOPNOTSUPP;
+	if (copy_from_user(&iov_cmd, useraddr, sizeof(iov_cmd)))
+		return -EFAULT;
+
+	ret = dev->ethtool_ops->iov_get_cmd(dev, &iov_cmd);
+	if (!ret)
+		ret = copy_to_user(useraddr, &iov_cmd, sizeof(iov_cmd));

	if (!ret && copy_to_user(...))
		ret = -EFAULT;
Quoted 2 lines
include/linux/ethtool.h +2 -0
+	return ret;
+}

[...]

Signature · 3 lines
Ben Hutchings, Staff Engineer, Solarflare
Not speaking for my employer; that's the marketing department's job.
They asked us to note that Solarflare product names are trademarked.
author
#3 lore raw
Quoted 40 lines

-----Original Message-----
From: Ben Hutchings [mailto:[email protected]]
Sent: Friday, October 07, 2011 5:38 PM
To: Rose, Gregory V
Cc: [email protected]
Subject: Re: [RFC PATCH V2 1/2] net/core/ethtool: New Commands to Configure IOV features

Quoted 31 lines · Greg Rose

The only currently supported method of configuring the number of VFs is through the max_vfs module parameter. This method is inadequate to support scenarios in which the user might wish to have varying numbers of VFs per PF. There is additional support for drivers that want to partition some driver resources to additional net devices and for configuring the number of Tx/Rx queue pairs per VF.

Signed-off-by Greg Rose <[email protected]>

---

 include/linux/ethtool.h |   30 +++++++++++++++++++++++++++++-
 net/core/ethtool.c      |   38 ++++++++++++++++++++++++++++++++++++++
 2 files changed, 67 insertions(+), 1 deletions(-)
include/linux/ethtool.h +9 -0
index 45f00b6..448730f 100644
@@ -720,6 +720,27 @@ enum ethtool_sfeatures_retval_bits {
 #define ETHTOOL_F_WISH          (1 << ETHTOOL_F_WISH__BIT)
 #define ETHTOOL_F_COMPAT        (1 << ETHTOOL_F_COMPAT__BIT)
 
+enum ethtool_iov_modes {
+	ETHTOOL_IOV_MODE_NONE,
+	ETHTOOL_IOV_MODE_SRIOV,
+	ETHTOOL_IOV_MODE_NETDEVS,
+};
+
+#define	ETHTOOL_IOV_CMD_CONFIGURE_SRIOV		1
+#define	ETHTOOL_IOV_CMD_CONFIGURE_NETDEVS	2
+#define	ETHTOOL_IOV_CMD_CONFIGURE_VF_QUEUES	3
Quoted 8 lines

include/linux/ethtool.h enum ethtool_sfeatures_retval_bits { · line 737

Quoted 6 lines
include/linux/ethtool.h +6 -0
+
+struct ethtool_iov_set_cmd {
+	__u32 cmd;
+	__u32 set_cmd;
+	__u32 cmd_param;
+};

Why introduce sub-commands?

For maximum flexibility. It's difficult (to me anyway) to foresee all the things we might want to configure for I/O virtualization features.

Quoted 7 lines

include/linux/ethtool.h enum ethtool_sfeatures_retval_bits { · line 742

Quoted 5 lines
include/linux/ethtool.h +4 -0
+struct ethtool_iov_get_cmd {
+	__u32 cmd;
+	__u32 mode;
+};

Why is it only possible to get the mode?

To my way of thinking it was the only interesting thing to query. I suppose I could also return the number of VFs or net devices along with the mode.

Quoted 4 lines

It really seems to make more sense to group these three parameters together and get/set them all at once. But if you can justify making them separate then struct ethtool_value is the type to use.

I can do that.

Quoted 2 lines

In any case, any new types or macros need comments.

OK.

Quoted 28 lines

[...]

Quoted 4 lines
include/linux/ethtool.h +4 -0
+static int ethtool_iov_get_command(struct net_device *dev,
+				  void __user *useraddr)
+{
+	int ret;

include/linux/ethtool.h

Quoted 10 lines
include/linux/ethtool.h +10 -0
+	struct ethtool_iov_get_cmd iov_cmd;
+
+	if (!dev->ethtool_ops->iov_get_cmd)
+		return -EOPNOTSUPP;
+	if (copy_from_user(&iov_cmd, useraddr, sizeof(iov_cmd)))
+		return -EFAULT;
+
+	ret = dev->ethtool_ops->iov_get_cmd(dev, &iov_cmd);
+	if (!ret)
+		ret = copy_to_user(useraddr, &iov_cmd, sizeof(iov_cmd));

	if (!ret && copy_to_user(...))
		ret = -EFAULT;

include/linux/ethtool.h

Quoted 2 lines
include/linux/ethtool.h +2 -0
+	return ret;
+}

[...]

--
Ben Hutchings, Staff Engineer, Solarflare
Not speaking for my employer; that's the marketing department's job. They asked us to note that Solarflare product names are trademarked.