You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Oct 26, 2022. It is now read-only.
This is just a couple notes to myself regarding some netlink-proto simplifications I've been contemplating for a while:
have a distinct codec for the audit protocol, instead of using feature flags
don't use the tokio codec trait? They force us to copy the data in intermediate buffers, which most of the time we don't need (unless we read multiple datagrams at once, like with the audit protocol).
have NetlinkFramed return a Result instead of an Option
rename NetlinkFramed into Transport maybe?
don't use unbounded channels? But then we have to handle errors when they get full. Not sure how to do that
This is just a couple notes to myself regarding some
netlink-proto
simplifications I've been contemplating for a while:NetlinkFramed
return aResult
instead of anOption
NetlinkFramed
intoTransport
maybe?Also:
Protocol.pending_requests
keep growing #138ENOBUFS
errors #139The text was updated successfully, but these errors were encountered: