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 v2 6/7] Driver: Vmxnet3: Introduce command to register memory region
Date: Thu, 19 May 2016 23:53:11 -0700 [thread overview]
Message-ID: <1463727192-4543-7-git-send-email-skhare@vmware.com> (raw)
In-Reply-To: <1463727192-4543-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 | 17 +++++++++++++++++
1 file changed, 17 insertions(+)
diff --git a/drivers/net/vmxnet3/vmxnet3_defs.h b/drivers/net/vmxnet3/vmxnet3_defs.h
index 274e145..c3a3164 100644
--- a/drivers/net/vmxnet3/vmxnet3_defs.h
+++ b/drivers/net/vmxnet3/vmxnet3_defs.h
@@ -81,6 +81,7 @@ enum {
VMXNET3_CMD_RESERVED2,
VMXNET3_CMD_RESERVED3,
VMXNET3_CMD_SET_COALESCE,
+ VMXNET3_CMD_REGISTER_MEMREGS,
VMXNET3_CMD_FIRST_GET = 0xF00D0000,
VMXNET3_CMD_GET_QUEUE_STATUS = VMXNET3_CMD_FIRST_GET,
@@ -668,6 +669,22 @@ struct Vmxnet3_CoalesceScheme {
} coalPara;
};
+struct Vmxnet3_MemoryRegion {
+ __le64 startPA;
+ __le32 length;
+ __le16 txQueueBits;
+ __le16 rxQueueBits;
+};
+
+#define MAX_MEMORY_REGION_PER_QUEUE 16
+#define MAX_MEMORY_REGION_PER_DEVICE 256
+
+struct Vmxnet3_MemRegs {
+ __le16 numRegs;
+ __le16 pad[3];
+ struct Vmxnet3_MemoryRegion memRegs[1];
+};
+
/* If the command data <= 16 bytes, use the shared memory directly.
* otherwise, use variable length configuration descriptor.
*/
--
2.8.2
next prev parent reply other threads:[~2016-05-20 6:53 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-05-20 6:53 [PATCH net-next v2 0/7] Driver: Vmxnet3: Version 3 Shrikrishna Khare
2016-05-20 6:53 ` [PATCH net-next v2 1/7] Driver: Vmxnet3: Prepare for version 3 changes Shrikrishna Khare
2016-05-20 6:53 ` [PATCH net-next v2 2/7] Driver: Vmxnet3: Introduce generic command interface to configure the device Shrikrishna Khare
2016-05-20 6:53 ` [PATCH net-next v2 3/7] Driver: Vmxnet3: Allow variable length Transmit Data ring buffer Shrikrishna Khare
2016-05-20 6:53 ` [PATCH net-next v2 4/7] Driver: Vmxnet3: Add Receive Data Ring support Shrikrishna Khare
2016-05-20 6:53 ` [PATCH net-next v2 5/7] Driver: Vmxnet3: Add support for get_coalesce, set_coalesce ethtool operations Shrikrishna Khare
2016-05-20 6:53 ` Shrikrishna Khare [this message]
2016-05-20 6:53 ` [PATCH net-next v2 7/7] Driver: Vmxnet3: Update to Version 3 Shrikrishna Khare
2016-05-23 21:00 ` [PATCH net-next v2 0/7] Driver: Vmxnet3: " 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=1463727192-4543-7-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).