From owner-freebsd-wireless@FreeBSD.ORG Fri Feb 15 07:49:48 2013 Return-Path: Delivered-To: freebsd-wireless@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by hub.freebsd.org (Postfix) with ESMTP id E1AE31C7; Fri, 15 Feb 2013 07:49:48 +0000 (UTC) (envelope-from monthadar@gmail.com) Received: from mail-wi0-x229.google.com (wi-in-x0229.1e100.net [IPv6:2a00:1450:400c:c05::229]) by mx1.freebsd.org (Postfix) with ESMTP id 4C9A1910; Fri, 15 Feb 2013 07:49:48 +0000 (UTC) Received: by mail-wi0-f169.google.com with SMTP id l13so969699wie.2 for ; Thu, 14 Feb 2013 23:49:46 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:x-received:in-reply-to:references:date:message-id :subject:from:to:cc:content-type; bh=qmPCTf9Wxe9PZ3SRCUhQTzW94pgpcn8itSw9neRY9po=; b=A9qi4OI8zrqE+cTYoVGUzX2ngNLfbvjYgQbRo/2kvLhceBnIwB461iZRMEU3lcUBHS y0LJT6uXl7uqWyKQH5zyPPllm8iF0cqq/7FeQ29HLoDLefXw01OXU20d29ymPPoa6uhD amuZpEDkUuCu8kB3qfwRAa8qYElusc1aNGKqFUFr1o6VburBu7YkFKPmaq2TCgR7s118 Gc/B9VU9ouhXZd1HnBf7naDRO3jqOm8zRFRWIJz/dPpBXAIVyALm+GOdMg6z0UCfga6L 8K1KytIjBczRpAVnRmCBtkTmToSIbxwqOyxsaWM0T8VhzjHcYE8Oj9Wf+oDFU3e78XTl xcBw== MIME-Version: 1.0 X-Received: by 10.180.97.166 with SMTP id eb6mr4054848wib.20.1360914586609; Thu, 14 Feb 2013 23:49:46 -0800 (PST) Received: by 10.227.59.19 with HTTP; Thu, 14 Feb 2013 23:49:46 -0800 (PST) In-Reply-To: References: Date: Fri, 15 Feb 2013 08:49:46 +0100 Message-ID: Subject: Re: [RFC] serialising net80211 TX From: Monthadar Al Jaberi To: Adrian Chadd Content-Type: text/plain; charset=ISO-8859-1 Cc: freebsd-wireless@freebsd.org X-BeenThere: freebsd-wireless@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: "Discussions of 802.11 stack, tools device driver development." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 15 Feb 2013 07:49:48 -0000 On Fri, Feb 15, 2013 at 2:49 AM, Adrian Chadd wrote: > On 14 February 2013 11:50, Monthadar Al Jaberi wrote: > >> Seems like the best architectural wise, first-in first out. I am just >> thinking of one can extend this too have like more than one queue, >> more like the QoS concept, and each packet have a time-stamp assigned >> to it.Would that help? > > Well, the queue thing is a bit orthogonal. Yes, we could run multiple > queues and multiple kernel threads. But what would multiple kernel > threads get us? I was thinking one kernel thread. This thread have some headroom to take from the higher priority queue if the frame on the other queue is not old "enough". > > > > Adrian -- Monthadar Al Jaberi