linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Shrikrishna Khare <skhare@vmware.com>
To: netdev@vger.kernel.org, linux-kernel@vger.kernel.org,
	pv-drivers@vmware.com
Cc: Shrikrishna Khare <skhare@vmware.com>, Guolin Yang <gyang@vmware.com>
Subject: [PATCH net-next v3 2/7] vmxnet3: introduce generic command interface to configure the device
Date: Mon, 13 Jun 2016 18:50:02 -0700	[thread overview]
Message-ID: <1465869007-10822-3-git-send-email-skhare@vmware.com> (raw)
In-Reply-To: <1465869007-10822-1-git-send-email-skhare@vmware.com>

Signed-off-by: Guolin Yang <gyang@vmware.com>
Signed-off-by: Shrikrishna Khare <skhare@vmware.com>
---
 drivers/net/vmxnet3/vmxnet3_defs.h | 22 +++++++++++++++++++++-
 1 file changed, 21 insertions(+), 1 deletion(-)

diff --git a/drivers/net/vmxnet3/vmxnet3_defs.h b/drivers/net/vmxnet3/vmxnet3_defs.h
index 8345e0c..a26a69d 100644
--- a/drivers/net/vmxnet3/vmxnet3_defs.h
+++ b/drivers/net/vmxnet3/vmxnet3_defs.h
@@ -79,6 +79,7 @@ enum {
 	VMXNET3_CMD_RESERVED1,
 	VMXNET3_CMD_LOAD_PLUGIN,
 	VMXNET3_CMD_RESERVED2,
+	VMXNET3_CMD_RESERVED3,
 
 	VMXNET3_CMD_FIRST_GET = 0xF00D0000,
 	VMXNET3_CMD_GET_QUEUE_STATUS = VMXNET3_CMD_FIRST_GET,
@@ -612,6 +613,18 @@ struct Vmxnet3_RxQueueDesc {
 	u8				      __pad[88]; /* 128 aligned */
 };
 
+struct Vmxnet3_SetPolling {
+	u8					enablePolling;
+};
+
+/* If the command data <= 16 bytes, use the shared memory directly.
+ * otherwise, use variable length configuration descriptor.
+ */
+union Vmxnet3_CmdInfo {
+	struct Vmxnet3_VariableLenConfDesc	varConf;
+	struct Vmxnet3_SetPolling		setPolling;
+	__le64					data[2];
+};
 
 struct Vmxnet3_DSDevRead {
 	/* read-only region for device, read by dev in response to a SET cmd */
@@ -630,7 +643,14 @@ struct Vmxnet3_DriverShared {
 	__le32				pad;
 	struct Vmxnet3_DSDevRead	devRead;
 	__le32				ecr;
-	__le32				reserved[5];
+	__le32				reserved;
+	union {
+		__le32			reserved1[4];
+		union Vmxnet3_CmdInfo	cmdInfo; /* only valid in the context of
+						  * executing the relevant
+						  * command
+						  */
+	} cu;
 };
 
 
-- 
2.8.2

  parent reply	other threads:[~2016-06-14  1:51 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-06-14  1:50 [PATCH net-next v3 0/7] vmxnet3: upgrade to version 3 Shrikrishna Khare
2016-06-14  1:50 ` [PATCH net-next v3 1/7] vmxnet3: prepare for version 3 changes Shrikrishna Khare
2016-06-14  1:50 ` Shrikrishna Khare [this message]
2016-06-14  1:50 ` [PATCH net-next v3 3/7] vmxnet3: allow variable length transmit data ring buffer Shrikrishna Khare
2016-06-14  1:50 ` [PATCH net-next v3 4/7] vmxnet3: add receive data ring support Shrikrishna Khare
2016-06-14  1:50 ` [PATCH net-next v3 5/7] vmxnet3: add support for get_coalesce, set_coalesce ethtool operations Shrikrishna Khare
2016-06-14 15:04   ` Ben Hutchings
2016-06-14  1:50 ` [PATCH net-next v3 6/7] vmxnet3: introduce command to register memory region Shrikrishna Khare
2016-06-14  5:54   ` Or Gerlitz
2016-06-14  1:50 ` [PATCH net-next v3 7/7] vmxnet3: update to version 3 Shrikrishna Khare
2016-06-14  5:52 ` [PATCH net-next v3 0/7] vmxnet3: upgrade " Or Gerlitz
2016-06-15  7:23 ` David Miller

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=1465869007-10822-3-git-send-email-skhare@vmware.com \
    --to=skhare@vmware.com \
    --cc=gyang@vmware.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=netdev@vger.kernel.org \
    --cc=pv-drivers@vmware.com \
    /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).