Currently a thread/task is used per connection, which limits the number of outstanding HTTP connections the driver can use. This should be turned into event-based code (using sk_data_ready of struct sock, no way to use epoll in kernel-space?).
It should be possible for every SRB volume to be backed by 10s or 100s of HTTP connections (potentially to different endpoints).
Currently a thread/task is used per connection, which limits the number of outstanding HTTP connections the driver can use. This should be turned into event-based code (using
sk_data_readyofstruct sock, no way to useepollin kernel-space?).It should be possible for every SRB volume to be backed by 10s or 100s of HTTP connections (potentially to different endpoints).