From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <jbrouer@redhat.com>
Received: from mx1.redhat.com (mx1.redhat.com [209.132.183.28])
	by huchra.bufferbloat.net (Postfix) with ESMTP id C32DC21F150
	for <cerowrt-devel@lists.bufferbloat.net>;
	Fri, 30 Aug 2013 08:46:43 -0700 (PDT)
Received: from int-mx12.intmail.prod.int.phx2.redhat.com
	(int-mx12.intmail.prod.int.phx2.redhat.com [10.5.11.25])
	by mx1.redhat.com (8.14.4/8.14.4) with ESMTP id r7UFkaWO029251
	(version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK);
	Fri, 30 Aug 2013 11:46:37 -0400
Received: from localhost (ovpn-116-39.ams2.redhat.com [10.36.116.39])
	by int-mx12.intmail.prod.int.phx2.redhat.com (8.14.4/8.14.4) with ESMTP
	id r7UFkYe4001178; Fri, 30 Aug 2013 11:46:34 -0400
Date: Fri, 30 Aug 2013 17:46:31 +0200
From: Jesper Dangaard Brouer <jbrouer@redhat.com>
To: Sebastian Moeller <moeller0@gmx.de>, Dave Taht <dave.taht@gmail.com>
Message-ID: <20130830174631.743e25ce@redhat.com>
In-Reply-To: <5BEF0C7C-C2F4-45A9-9FF2-E32A05B8D67B@gmx.de>
References: <CAA93jw7rankvo0B7+HzbASYY2gBcQfa2B-_dC2z6CHhqfWSkJQ@mail.gmail.com>
	<56B261F1-2277-457C-9A38-FAB89818288F@gmx.de>
	<CAA93jw6ku0OOXzNcAUtK4UL5uc7R2zVAOKo1+Fwzmr7gCH1pzA@mail.gmail.com>
	<2148E2EF-A119-4499-BAC1-7E647C53F077@gmx.de>
	<03951E31-8F11-4FB8-9558-29EAAE3DAE4D@gmx.de>
	<CAA93jw6PS1rQqxPTfroW9J1tOrp8gWE1G98mYkKCNTAvPoYrAg@mail.gmail.com>
	<9A9B094D-CA07-48B0-85FE-FA7C759FEDE3@gmx.de>
	<CAA93jw5-Dv7NTh-bU6BK=huWtpo6DKCBfEG7nFDjHEOnqi0wJw@mail.gmail.com>
	<5BEF0C7C-C2F4-45A9-9FF2-E32A05B8D67B@gmx.de>
Organization: Red Hat Inc.
Mime-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
X-Scanned-By: MIMEDefang 2.68 on 10.5.11.25
Cc: "cerowrt-devel@lists.bufferbloat.net" <cerowrt-devel@lists.bufferbloat.net>
Subject: Re: [Cerowrt-devel] some kernel updates + new userspace patch
X-BeenThere: cerowrt-devel@lists.bufferbloat.net
X-Mailman-Version: 2.1.13
Precedence: list
List-Id: Development issues regarding the cerowrt test router project
	<cerowrt-devel.lists.bufferbloat.net>
List-Unsubscribe: <https://lists.bufferbloat.net/options/cerowrt-devel>,
	<mailto:cerowrt-devel-request@lists.bufferbloat.net?subject=unsubscribe>
List-Archive: <https://lists.bufferbloat.net/pipermail/cerowrt-devel>
List-Post: <mailto:cerowrt-devel@lists.bufferbloat.net>
List-Help: <mailto:cerowrt-devel-request@lists.bufferbloat.net?subject=help>
List-Subscribe: <https://lists.bufferbloat.net/listinfo/cerowrt-devel>,
	<mailto:cerowrt-devel-request@lists.bufferbloat.net?subject=subscribe>
X-List-Received-Date: Fri, 30 Aug 2013 15:46:44 -0000


[long-thread-cut]

Sebastian, noted at some point that is was difficult to determine if
the tc configuration were using the linklayer option.

I have posted a patch against iproute2/tc, that implement reading out
the linklayer setting (requires my kernel patch discussed in this
thread).

See:
 http://thread.gmane.org/gmane.linux.network/281876

This patch also sends the linklayer option to the kernel directly,
which mean that the kernel don't need to perform linklayer detection
based on the rate table (which were not accurate at rates above
100Mbit/s).

-- 
Best regards,
  Jesper Dangaard Brouer
  MSc.CS, Sr. Network Kernel Developer at Red Hat
  Author of http://www.iptv-analyzer.org
  LinkedIn: http://www.linkedin.com/in/brouer