| To: | Vladimir Kondratiev <vkondra@xxxxxxx> |
|---|---|
| Subject: | Re: generic 802.11 stack |
| From: | "David S. Miller" <davem@xxxxxxxxxxxxx> |
| Date: | Tue, 7 Sep 2004 12:10:19 -0700 |
| Cc: | netdev@xxxxxxxxxxx |
| In-reply-to: | <200409072141.58893.vkondra@xxxxxxx> |
| References: | <200408312111.02438.vda@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxx> <200409072106.28334.vkondra@xxxxxxx> <20040907110813.6b463f3a.davem@xxxxxxxxxxxxx> <200409072141.58893.vkondra@xxxxxxx> |
| Sender: | netdev-bounce@xxxxxxxxxxx |
On Tue, 7 Sep 2004 21:41:54 +0300 Vladimir Kondratiev <vkondra@xxxxxxx> wrote: > This should be done in generic way. This information used to communicate > berween particular driver and generic stack. For example, Rx PHY info and Tx > status info should be used for in-stack generic rate scaling algorithm. > > To complicate it a bit, cb[] is only 48 bytes long. PHY info may easily > exceed > this size, so it's better to allocate something and free it in destructor. > > But again, point is this structure should be generic since it is used by > stack. TCP does the same thing, and if space is an issue you can use pointers in the cb[] area, other subsystems do this. |
| Previous by Date: | Re: generic 802.11 stack, Vladimir Kondratiev |
|---|---|
| Next by Date: | Re: generic 802.11 stack, Vladimir Kondratiev |
| Previous by Thread: | Re: generic 802.11 stack, Vladimir Kondratiev |
| Next by Thread: | Re: generic 802.11 stack, Vladimir Kondratiev |
| Indexes: | [Date] [Thread] [Top] [All Lists] |