From owner-freebsd-wireless@FreeBSD.ORG Thu Feb 28 23:38:22 2013 Return-Path: Delivered-To: freebsd-wireless@freebsd.org Received: from mx1.freebsd.org (mx1.FreeBSD.org [8.8.178.115]) by hub.freebsd.org (Postfix) with ESMTP id 49935EB0 for ; Thu, 28 Feb 2013 23:38:22 +0000 (UTC) (envelope-from adrian.chadd@gmail.com) Received: from mail-wg0-f53.google.com (mail-wg0-f53.google.com [74.125.82.53]) by mx1.freebsd.org (Postfix) with ESMTP id E08CB974 for ; Thu, 28 Feb 2013 23:38:21 +0000 (UTC) Received: by mail-wg0-f53.google.com with SMTP id fn15so1970919wgb.20 for ; Thu, 28 Feb 2013 15:38:20 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:x-received:sender:date:x-google-sender-auth:message-id :subject:from:to:content-type; bh=su9Ipnm9sUbILPYaKFTd2vCC84Z9YEvWmOSktftGa1U=; b=w5kEgnCbXvEFB86HuhEEBe67Ur5e9JcBrYP6KAtmQUzQ8+l2YLv2Wqk9onRJigV4u9 zs+MkcWzTEUIaAj6cdK25LjoYgdHImd8nXWYgBHHKuyqQQ+35PFRM1K6ipwFfPrggUe7 UnmoJqJlUokrh9dqGNmdFMOEcSlnA/fVF5P4I5zHlxvCCqiXSspmiNpSbCduAME7sPyf APGJZEpilqifRE8JhnhSoJBQFApR0mTiq1Ve1l/0Ga/57FdKrhIajppEZvBgJuzE8x0H eiWCEnxOphaqy2ZczW6IUtSD+O0Rnn2BWcEznpXfsA4RzfMTP5ORKMa4yE4ao3yB5xIN K1ug== MIME-Version: 1.0 X-Received: by 10.180.73.238 with SMTP id o14mr624583wiv.32.1362094700711; Thu, 28 Feb 2013 15:38:20 -0800 (PST) Sender: adrian.chadd@gmail.com Received: by 10.216.114.201 with HTTP; Thu, 28 Feb 2013 15:38:20 -0800 (PST) Date: Thu, 28 Feb 2013 15:38:20 -0800 X-Google-Sender-Auth: L8RShp7Cp2ReKHc1KA26wGwVV_g Message-ID: Subject: [RFC] replace ic->ic_raw_xmit() calls with a method - ieee80211_raw_xmit() From: Adrian Chadd To: freebsd-wireless@freebsd.org Content-Type: text/plain; charset=ISO-8859-1 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: Thu, 28 Feb 2013 23:38:22 -0000 Hi, As part of eventually making ic_raw_xmit() go via the vap/ic queue, I'd like to methodise this. Right now the stack calls ic->ic_raw_xmit(ni, mbuf, params) directly. I'd like to stick it inside a method call. Later on the raw frames can be queued via the VAP TX queue and processed in-order. This doesn't (yet) deal with all of the odd locking and serialisation issues; it's just to avoid calling that driver method direct. Comments? Does anyone have a problem with this? Thanks, Adrian