DPDK patches and discussions
 help / color / mirror / Atom feed
From: Hiroshi Shimamoto <h-shimamoto@ct.jp.nec.com>
To: "dev@dpdk.org" <dev@dpdk.org>
Cc: Hayato Momma <h-momma@ce.jp.nec.com>
Subject: [dpdk-dev] [memnic PATCH 1/5] common: update memnic.h to support variable frame size
Date: Fri, 6 Jun 2014 11:05:11 +0000	[thread overview]
Message-ID: <7F861DC0615E0C47A872E6F3C5FCDDBD0110212E@BPXM14GP.gisp.nec.co.jp> (raw)

From: Hiroshi Shimamoto <h-shimamoto@ct.jp.nec.com>

Update MEMNIC data structure in common header file.

Prepare to support extra features for MEMNIC.

Change name reserved to request which will be used to negotiate between
host and guest, and add feature flag and other definitions.

Signed-off-by: Hiroshi Shimamoto <h-shimamoto@ct.jp.nec.com>
Reviewed-by: Hayato Momma <h-momma@ce.jp.nec.com>
---
 common/memnic.h | 9 +++++++--
 1 file changed, 7 insertions(+), 2 deletions(-)

diff --git a/common/memnic.h b/common/memnic.h
index 84e941c..d5a651f 100644
--- a/common/memnic.h
+++ b/common/memnic.h
@@ -42,19 +42,24 @@
 #define MEMNIC_MAX_PACKET_SIZE	(4096)
 
 #define MEMNIC_MAX_FRAME_LEN	(1500 + 14 + 4) /* MTU + ether header + vlan */
+#define MEMNIC_MAX_JUMBO_FRAME_LEN	(MEMNIC_MAX_PACKET_SIZE - 8)
 
 struct memnic_header {
 	uint32_t magic;
 	uint32_t version;
 	uint32_t valid;
 	uint32_t reset;
-	uint32_t features;
-	uint32_t reserved;
+	uint32_t features;	/* features this MEMNIC provides */
+	uint32_t request;	/* requesting features from Guest */
 	union {
 		uint8_t mac_addr[6];
 		uint8_t dummy[8];
 	};
+	/* for extra features */
+	uint32_t framesz;
 };
+#define MEMNIC_FEAT_FRAME_SIZE	(0x00000001)
+#define MEMNIC_FEAT_ALL		(MEMNIC_FEAT_FRAME_SIZE)
 
 struct memnic_info {
 	uint32_t flags;
-- 
1.8.4

                 reply	other threads:[~2014-06-06 11:08 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=7F861DC0615E0C47A872E6F3C5FCDDBD0110212E@BPXM14GP.gisp.nec.co.jp \
    --to=h-shimamoto@ct.jp.nec.com \
    --cc=dev@dpdk.org \
    --cc=h-momma@ce.jp.nec.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).