From: Minetti V. <val...@ml...> - 2005-01-25 16:32:27
|
ok, i'm looking at the code.. for now i've figured out that First step: set get parameter. I have to write 2 functions from the scratch and put them here:=20 (taken from acx100_ioctl.c) (iw_handler) NULL /* acx_ioctl_set_frag FIXME */, /* SIOCSIWFRAG */ (iw_handler) NULL /* acx_ioctl_get_frag FIXME */, /* SIOCGIWFRAG */ they should read and write the frag threshold attribute (described in = wlandevice.h ? ). Second step: use of this parameter.=20 a) (TX) when the data is transmitted i have to split it in chunks of = thresohold size modifying the field that holds the fragment sequence = number and looping the transmission while all fragments are received = succesfully (ap should reply an ACK) b) (RX) recognize that a packet is part of a fragment burst, receive, = reorder and assembly of the package. (are there chanches that packets = are received out of order?) is it correct? |
From: Andreas M. <an...@us...> - 2005-01-25 19:31:20
|
Hi, On Tue, Jan 25, 2005 at 05:31:24PM +0100, Minetti Valerio wrote: > ok, i'm looking at the code.. for now i've figured out that > > First step: set get parameter. > I have to write 2 functions from the scratch and put them here: > (taken from acx100_ioctl.c) > > (iw_handler) NULL /* acx_ioctl_set_frag FIXME */, /* SIOCSIWFRAG */ > (iw_handler) NULL /* acx_ioctl_get_frag FIXME */, /* SIOCGIWFRAG */ > > they should read and write the frag threshold attribute (described in wlandevice.h ? ). Yup, easy, many other functions do the (almost) same thing... > Second step: use of this parameter. > a) (TX) when the data is transmitted i have to split it in chunks of thresohold size modifying the field that holds the fragment sequence number and looping the transmission while all fragments are received succesfully (ap should reply an ACK) Yup, something like that. > b) (RX) recognize that a packet is part of a fragment burst, receive, reorder and assembly of the package. (are there chanches that packets are received out of order?) Yup, same here. Note that this may have been a large source of problems, since our driver doesn't support Rx defrag. > is it correct? AFAICS yes (but I'm far from knowledgeable on this area). Andreas Mohr |