From owner-freebsd-wireless@FreeBSD.ORG Mon Feb 18 10:05:23 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 54745169; Mon, 18 Feb 2013 10:05:23 +0000 (UTC) (envelope-from monthadar@gmail.com) Received: from mail-wi0-f176.google.com (mail-wi0-f176.google.com [209.85.212.176]) by mx1.freebsd.org (Postfix) with ESMTP id AB74E8D7; Mon, 18 Feb 2013 10:05:22 +0000 (UTC) Received: by mail-wi0-f176.google.com with SMTP id hm14so3239199wib.3 for ; Mon, 18 Feb 2013 02:05:15 -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=fxkbG3MPoS7TMoywqmgfxmLBCS+LdYO6IwyLBuXR0Wk=; b=uoPHbe5bZKZ2kuq6eb1jnIM7tP9UPV+sfiri6ajjbIEhj0ObM2Aj+bglBsTL5XN/Dc FXvqu+gGspJzgg1gbnbq2Ro6GWpOGCElSKKmePQPOEYHuhU8Ra+7G7xCDmnncU/ekm8+ B3RFcZ6dvMvpYwKttvukW68ccI9D4xjIzQjLFNG4+q0cwcPacPVxF+YQ3420uA3yqIBD dCOv3cbz65Ca5c4LyESE9q6zHjwrz/Unh6HaiUoyHYCxtoJveGQd+PsEFsEkv4imxHRC JKFjRJFMocxiSHPUAxC8yHyEMNj3U6nbnfq3Azx5ALYrgk+j37tSAjnqpZLHD7TtwMwI TIow== MIME-Version: 1.0 X-Received: by 10.180.7.232 with SMTP id m8mr17026516wia.8.1361181915894; Mon, 18 Feb 2013 02:05:15 -0800 (PST) Received: by 10.227.196.15 with HTTP; Mon, 18 Feb 2013 02:05:15 -0800 (PST) In-Reply-To: References: Date: Mon, 18 Feb 2013 11:05:15 +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: PseudoCylon , 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: Mon, 18 Feb 2013 10:05:23 -0000 On Sun, Feb 17, 2013 at 1:46 AM, Adrian Chadd wrote: > Here's version two of the patch: it includes the rest of the TX paths > locked as well as some extra assertions about the state of the TX lock > requirements. Why not make ieee80211_start_pkt public? So that we can call it from mesh_transmit_to_gate in mesh.c? > > I've only lightly tested this in STA mode. I haven't yet really tested > this in hostap mode. I gather it's going to panic all the things. > Thus, please only run this on a test device. :-) > > > > Adrian -- Monthadar Al Jaberi