Skip to content
This repository has been archived by the owner on Jan 15, 2021. It is now read-only.

ThaliCore: implement max VirtualSocket limit #1933

Open
enricogior opened this issue Jul 11, 2017 · 0 comments
Open

ThaliCore: implement max VirtualSocket limit #1933

enricogior opened this issue Jul 11, 2017 · 0 comments
Assignees

Comments

@enricogior
Copy link
Member

The max number of overall connections in the native layer is limited by the number of concurrent virtual sockets: each virtual socket adds an entry to RunLoop and the max number of entries per process is 64, that is enforced by the OS.
Adding more than 64 entries doesn't trigger an error in RunLoop, simply the entries after the 64th will not be scheduled until other entries have been removed.

Given one entry in RunLoop is alrady taken for another workitem, it would be safe to limit the max virtual sockets to 62.

@enricogior enricogior self-assigned this Jul 11, 2017
@enricogior enricogior changed the title ThaliCore: implement max VirtualSocket check ThaliCore: implement max VirtualSocket limit Jul 11, 2017
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

1 participant