On 9 nov 2011 16:28 "Simon Goldschmidt" <[email protected]> wrote:
> Mason <[email protected]> wrote: > > SO_PRIORITY (and setsockopt) might be useful? > > > > The following document might also be relevant. > > <https://trac.pjsip.org/repos/wiki/QoS> > > Thanks, that's very helpful! I guess SO_PRIORITY would be fine for us, > then. That is, if we find a nice way to implmenet it on pcb-level. > > Simon > > Nice document you found Mason! It really sums it up. With that solution it looks like TOS and PCP can be set independently and per socket, which is what we need. Simon: Good idea about the addr_hint mechanism you mentioned earlier. Communicating information from socket layer to netif layer by setting/resetting an essentially global variable per frame may perhaps not be the most elegant solution, but since it is already in place... (Adding too many arguments to functions is not very nice either..) A couple of ideas: Instead of netif->addr_hint pointing to the pcb.addr_hint, how about replacing netif->addr_hint with a netif->pcb? That way it could be used to access both addr_hint and QoS information in the pcb. The disadvantage is that it would take perhaps one more instruction to access the addr_hint. Another option could be to change all the places in lwip where the netif->addr_hint is set/reset today, to a function macro which takes a netif and a pcb as arguments. That way the function macro can be redefined to copy any necessary variables from pcb to netif, without ever having to change all the set/reset locations in lwip again. These are just a few ideas, I have not tried them out in code. Regards, Timmy Brolin
_______________________________________________ lwip-users mailing list [email protected] https://lists.nongnu.org/mailman/listinfo/lwip-users
