[dpdk-dev] [PATCH] eal: add option to not store segment fd's

David Marchand david.marchand at redhat.com
Fri Mar 29 10:50:58 CET 2019

On Fri, Feb 22, 2019 at 6:12 PM Anatoly Burakov <anatoly.burakov at intel.com>

> Due to internal glibc limitations [1], DPDK may exhaust internal
> file descriptor limits when using smaller page sizes, which results
> in inability to use system calls such as select() by user
> applications.
> While the problem can be worked around using --single-file-segments
> option, it does not work if --legacy-mem mode is also used. Add a
> (yet another) EAL flag to disable storing fd's internally. This
> will sacrifice compability with Virtio with vhost-backend, but
> at least select() and friends will work.
> [1] https://mails.dpdk.org/archives/dev/2019-February/124386.html

Sorry, I am a bit lost and I never took the time to look in the new memory
allocation system.
This gives the impression that we are accumulating workarounds, between
legacy-mem, single-file-segments, now no-seg-fds.

Iiuc, everything revolves around the need for per page locks.
Can you summarize why we need them?


David Marchand

More information about the dev mailing list