> We definitely would implement security in user space but have not > decided yet were to draw the line. I think that it makes sense at least > to have path discovery in-kernel, since there is a lot of activity on > them (each path is rebuilt every few seconds and there can be many of > them) and many path discovery frames just need to be forwarded and do > not have to be transferred to user space. Sounds reasonable. > AFAIK, it would only be necessary to move part of the peer link > establishment to user space. Path discovery takes place after the peer > links have been established. Yes, ok, that makes sense then. I suppose we'll then have to "rewrite" the peer link establishment in userspace once we want to work on that but I think it's fine to have it in the kernel too for basic mesh functionality, we need to shake out the userspace MLME first (though it shouldn't be too much work any more.) johannes
Attachment:
signature.asc
Description: This is a digitally signed message part
