Date: Thu, 3 Sep 2015 18:00:41 +0300 From: Gleb Smirnoff <glebius@FreeBSD.org> To: Andriy Voskoboinyk <s3erios@gmail.com>, Adrian Chadd <adrian@freebsd.org> Cc: "net@freebsd.org" <net@freebsd.org> Subject: Re: mbufq-less iwn(4) Message-ID: <20150903150041.GR1023@glebius.int.ru> In-Reply-To: <op.x4d4ddkxiew4ia@localhost> References: <20150901112043.GB1023@glebius.int.ru> <CAJ-Vmokn91fHQyg-AGqCgccRoMS89TuWpQ9RuxL%2B9nmgt%2BX2kQ@mail.gmail.com> <20150902060324.GF1023@glebius.int.ru> <op.x4d4ddkxiew4ia@localhost>
next in thread | previous in thread | raw e-mail | index | archive | help
On Thu, Sep 03, 2015 at 05:11:27PM +0300, Andriy Voskoboinyk wrote: A> > A> Other thing - ic_transmit() also needs to handle fragments, like I do A> > A> with ath. Ie, handing it a list of packets is actually a list of A> > A> 802.11 fragments, rather than separate MPDUs. A> > A> A> > A> Another thing - we're modifying the mbufs (adding 802.11 data to it) A> > A> before we pass them to the driver, and if the driver fails to A> > A> transmit, we can't just pass it back up the net80211 stack to the tcp A> > A> or udp layer.. A> > A> > Sure, stack probably would need to strip the data. Anyway, that's A> > a future task. A> > A> A> What about https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=193569 ? I'd leave that to you, guys :) I don't want to go knee deep into the 802.11, I'm just working on a "tiny" project of opaque struct ifnet :) -- Totus tuus, Glebius.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20150903150041.GR1023>