From owner-freebsd-wireless@FreeBSD.ORG Sun Apr 14 11:27:21 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 1CA42B27 for ; Sun, 14 Apr 2013 11:27:21 +0000 (UTC) (envelope-from monthadar@gmail.com) Received: from mail-wi0-x235.google.com (mail-wi0-x235.google.com [IPv6:2a00:1450:400c:c05::235]) by mx1.freebsd.org (Postfix) with ESMTP id AF06DB1B for ; Sun, 14 Apr 2013 11:27:20 +0000 (UTC) Received: by mail-wi0-f181.google.com with SMTP id hj8so748015wib.2 for ; Sun, 14 Apr 2013 04:27:19 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:x-received:date:message-id:subject:from:to :content-type; bh=1eTbOsp/vUERTVQcg+lU1UR2ei/w5xXPhGG1AaCcPQ8=; b=kD84ZbEqhGe7pyjIG6aLji/txt00H3MAI7/x5nLHaOZ7ISzj7jryM2jb2Z0PlBd7da K3e9xQJcIxEfOBKM8C++XZscrCb1fcaQnEp+a3bX24AbjrbrwkOu60VFpGT3lhLnYn+2 66CCQYr1S4iKIXG//oFpZHYFBQDgUBt3+iuH3U8m7Rks+64M+KKvu0UYYI7alzoVimte C3sqGKEnaUpqwnZfFKPaeWzAwx0GH+YemC1IP4OlmB3b2NwWFSPW+SqgrVn0MSNx15z3 KAR9G6G6Srxn8+Ifi58LX7JcmQ4XG1EtHWbu5so6OL4tKmJU59H3hwuaQnrxpMuLLTEK 9FWQ== MIME-Version: 1.0 X-Received: by 10.194.172.71 with SMTP id ba7mr26486330wjc.26.1365938839790; Sun, 14 Apr 2013 04:27:19 -0700 (PDT) Received: by 10.227.107.70 with HTTP; Sun, 14 Apr 2013 04:27:19 -0700 (PDT) Date: Sun, 14 Apr 2013 13:27:19 +0200 Message-ID: Subject: 802.11 TX Path && mesh data forwarding From: Monthadar Al Jaberi To: freebsd-wireless@freebsd.org Content-Type: text/plain; charset=ISO-8859-1 X-Content-Filtered-By: Mailman/MimeDel 2.1.14 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: Sun, 14 Apr 2013 11:27:21 -0000 Hi everyone, I would like to bring up an issue me and Adrian have been thinking bout for some time now. It has to do with the recent TX path code re-write Adrian have been working on and how that affects the 802.11 mesh code. And what is the best solution for handling data frame forwarding. I think mesh_forward need to be refactored and modified. And basically just after duplicating the data frame and decrementing TTL we need to queue the frame somehow. This frame is an 802.11 frame that needs to go through the same low level TX processing a frame coming down from the stack go through. We need to mark the mbuf containing the frame somehow so we skip some steps in the normal TX path. Or maybe we need to add a new queue or something similar. Any thoughts are much appreciated. -- Monthadar Al Jaberi