From owner-freebsd-current@FreeBSD.ORG  Mon Sep 26 15:30:28 2011
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Delivered-To: freebsd-current@freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34])
	by hub.freebsd.org (Postfix) with ESMTP id 7B1AB106566C;
	Mon, 26 Sep 2011 15:30:28 +0000 (UTC)
	(envelope-from adrian.chadd@gmail.com)
Received: from mail-gw0-f54.google.com (mail-gw0-f54.google.com [74.125.83.54])
	by mx1.freebsd.org (Postfix) with ESMTP id 15B0F8FC08;
	Mon, 26 Sep 2011 15:30:27 +0000 (UTC)
Received: by gwj18 with SMTP id 18so5745196gwj.13
	for <multiple recipients>; Mon, 26 Sep 2011 08:30:27 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma;
	h=mime-version:sender:in-reply-to:references:date
	:x-google-sender-auth:message-id:subject:from:to:cc:content-type
	:content-transfer-encoding;
	bh=m1HHkqo3DZ6gBYuYQ6DrTXCBLK4ZNoKYg3mhhfKRCFM=;
	b=RKfJulW/1te8ZZApmSfV68hn+LhLMe+c2UDR6kAuwjeiYZLDTXuQitTrNtGei9hgid
	vfcaqCeA7NPp7X6cFo5koBQ0SwCc3r6fwui0yf4MjApXbrkKmvAjvoeGZ7tGCgLan+l8
	5EXb8mS4efd0Ayp5O7qaN1Kc/0sFGcsG38StI=
MIME-Version: 1.0
Received: by 10.236.193.72 with SMTP id j48mr19498906yhn.21.1317051027533;
	Mon, 26 Sep 2011 08:30:27 -0700 (PDT)
Sender: adrian.chadd@gmail.com
Received: by 10.236.111.42 with HTTP; Mon, 26 Sep 2011 08:30:27 -0700 (PDT)
In-Reply-To: <201109261053.30410.jhb@freebsd.org>
References: <CAJ-VmomZyDJV62yCQOvG=UB6H4wfz9=3_cWzEL7vWAA14TCyYA@mail.gmail.com>
	<201109260917.44236.jhb@freebsd.org>
	<CAJ-Vmom721ndMmSihA=58Fux-JBWHo1rA82FXYa__mmaRMW=tQ@mail.gmail.com>
	<201109261053.30410.jhb@freebsd.org>
Date: Mon, 26 Sep 2011 23:30:27 +0800
X-Google-Sender-Auth: VxmY6we6hrZ6YM4EzT1soh80x5o
Message-ID: <CAJ-VmomyMQpcpHo4ve-_O67_8VVJW-YRqWeb-7exSxzV5rz_pA@mail.gmail.com>
From: Adrian Chadd <adrian@freebsd.org>
To: John Baldwin <jhb@freebsd.org>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
Cc: Alexander Motin <mav@freebsd.org>, freebsd-current@freebsd.org
Subject: Re: ath / 802.11n performance issues and timer code
X-BeenThere: freebsd-current@freebsd.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Discussions about the use of FreeBSD-current
	<freebsd-current.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>, 
	<mailto:freebsd-current-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-current>
List-Post: <mailto:freebsd-current@freebsd.org>
List-Help: <mailto:freebsd-current-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>,
	<mailto:freebsd-current-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Mon, 26 Sep 2011 15:30:28 -0000

On 26 September 2011 22:53, John Baldwin <jhb@freebsd.org> wrote:

> I meant do the timer settings affect UDP performance? =A0I.e. does idleti=
ck=3D1
> change UDP performance at all?

I'll check that and get back to you.

But please keep in mind that the first time I tried this and saw
immediate results was with the device in hostap mode - where ethernet
and wlan0 are bridged via if_bridge.
There's no TCP or UDP state being handled at all.

>> Which should wake up a/the taskqueue thread in question and have it
>> immediately run the next task on the queue. The taskqueue doesn't have
>> any form of timer/callout; it's just a "submit this to get run." When
>> will it be run? I hope not at the next tick, not if the CPU is free.
>
> No, that scheduling is synchronous. =A0Anytime a thread is scheduled the
> scheduler will check if it should preempt the current thread to run the
> new thread.

I admit I don't quite understand yet the scheduler and event/timer
handling code. What about if nothing is currently scheduled and the
CPU is idle? When will the idle process get tickled? I assume it would
preempt the idle process immediately and run the taskqueue kernel
thread, right? Would there ever be a situation where it doesn't do
this?



Adrian