All of lore.kernel.org
 help / color / mirror / Atom feed
From: ANNIE LI <annie.li@oracle.com>
To: James Harper <james.harper@bendigoit.com.au>
Cc: xen-devel@lists.xensource.com
Subject: Re: Is 802.1p surpported by xen?
Date: Wed, 08 Apr 2009 10:27:13 +0800	[thread overview]
Message-ID: <49DC0B81.9020809@oracle.com> (raw)
In-Reply-To: <AEC6C66638C05B468B556EA548C1A77D0162CFFD@trantor>


[-- Attachment #1.1: Type: text/plain, Size: 1933 bytes --]


James Harper wrote:
> How are you trying to support this? It should be as simple as telling Windows that it is supported and then maintaining different packet queues in your driver. I don't think that there is any state information that is shared between different adapters.
>
> What happens on the backend interface and beyond is pretty much beyond your control, but as long as they respect the priority tags it should be fine, and even if they don't at least you have transmitted the packets based on the priority so you've done your bit.
It is a requirement for NDIS6.0 driver when testing NDISTest 
6.0(priority). Only a warning reported for NDIS5.1 driver.

The server side will send packets with Non-Zero priority, and client 
side will check whether the packets received is with correct priority or 
not. So if keep a different queue in miniport dirver, miniport can not 
put the priority tag in the frame, and receive side still fails to 
receive the correct priority tag packets.

Following information is i googled:

The specific NDIS structure is NDIS_NET_BUFFER_LIST_8021Q_INFO 
<http://msdn2.microsoft.com/en-us/library/bb245890.aspx>, which contains 
member variables for both VlanID and UserPriority, and is passed to the 
NDIS miniport driver for implementing both priority tagging 
(UserPriority) and VLAN (VlanId). It is up to the NDIS miniport driver 
to actually insert the 802.1Q tag into the frame based on these values 
before transmitting on the wire. A miniport driver will only insert this 
tag if the feature is supported and enabled in the advanced properties 
of the NIC driver;

The miniport drivers must strip the tag when received, and populate the 
NDIS_NET_BUFFER_LIST_8021Q_INFO UserPriority and VlanId fields with the 
values in the tag.

Details is in 
http://social.msdn.microsoft.com/forums/en-US/networkqosqwave/thread/a774a51c-6c6b-4374-a190-48153b5a74f7/

Any suggestions?

Thanks
Annie.



[-- Attachment #1.2: Type: text/html, Size: 2692 bytes --]

[-- Attachment #2: Type: text/plain, Size: 138 bytes --]

_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xensource.com
http://lists.xensource.com/xen-devel

  reply	other threads:[~2009-04-08  2:27 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-04-07  8:17 Is 802.1p surpported by xen? ANNIE LI
2009-04-07  9:10 ` James Harper
2009-04-08  2:27   ` ANNIE LI [this message]
2009-04-08  3:28     ` James Harper
2009-04-08  4:32       ` ANNIE LI
2009-04-08 11:23         ` ANNIE LI

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=49DC0B81.9020809@oracle.com \
    --to=annie.li@oracle.com \
    --cc=james.harper@bendigoit.com.au \
    --cc=xen-devel@lists.xensource.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.