From owner-freebsd-net@FreeBSD.ORG  Fri Jan 21 03:34:38 2005
Return-Path: <owner-freebsd-net@FreeBSD.ORG>
Delivered-To: freebsd-net@freebsd.org
Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125])
	by hub.freebsd.org (Postfix) with ESMTP
	id 02EEA16A4CE; Fri, 21 Jan 2005 03:34:38 +0000 (GMT)
Received: from mail.ntmk.ru (mail.ntmk.ru [217.114.241.6])
	by mx1.FreeBSD.org (Postfix) with ESMTP
	id 7B00743D46; Fri, 21 Jan 2005 03:34:37 +0000 (GMT)
	(envelope-from boris@ntmk.ru)
Received: from boris.nikom.ru ([10.1.16.195])
	by mail.ntmk.ru with esmtp (Exim 4.34)
	id 1CrpZE-0005v6-36; Fri, 21 Jan 2005 08:34:36 +0500
Message-ID: <41F0784B.4040109@ntmk.ru>
Date: Fri, 21 Jan 2005 08:34:35 +0500
From: Boris Kovalenko <boris@ntmk.ru>
User-Agent: Mozilla Thunderbird 1.0 (X11/20041228)
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: Andre Oppermann <andre@freebsd.org>, freebsd-net@freebsd.org
References: <41EF2B6C.2090609@ntmk.ru> <41F01547.35D1B582@freebsd.org>
In-Reply-To: <41F01547.35D1B582@freebsd.org>
Content-Type: text/plain; charset=KOI8-R; format=flowed
Content-Transfer-Encoding: 7bit
Subject: Re: [PATCH] 802.1p priority
X-BeenThere: freebsd-net@freebsd.org
X-Mailman-Version: 2.1.1
Precedence: list
List-Id: Networking and TCP/IP with FreeBSD <freebsd-net.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-net>,
	<mailto:freebsd-net-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-net>
List-Post: <mailto:freebsd-net@freebsd.org>
List-Help: <mailto:freebsd-net-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-net>,
	<mailto:freebsd-net-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Fri, 21 Jan 2005 03:34:38 -0000

Andre Oppermann wrote:
>>is this enough for BSD community or should I look and patch something more?
> Not a bad idea. :-)
Thanks :)
> 
> To make it perfect the packet priority should be settable from anywhere
> in the system (ipfw, dummynet, pf, etc.) through a mtag and then inserted
> into the ethernet frame header.  And it should for for "untagged" frames
> too.  You don't have to code that though. ;-)
Hmmm... I have no knowledge how to do so. If You point me to docs I'll 
read.
> 
> Please file this patch as PR and post the PR number so we don't forget
> about it.
Ok, I'll do it more complex. Now, the vlan driver honor the 802.1Q 
specification and forgot about CFI field too. Yes, it mostly is 0, but 
someone (especially in FDDI enviroment) may want to set it to 1. So my 
next patch will allow to set CFI & 802.1p fields.
> 


-- 
With respect,
	Boris