From: Iain Barker <iain.barker@oracle.com>
To: "Wiles, Keith" <keith.wiles@intel.com>
Cc: "dev@dpdk.org" <dev@dpdk.org>,
"edwin.leung@oracle.com" <edwin.leung@oracle.com>
Subject: Re: [dpdk-dev] Question about DPDK hugepage fd change
Date: Tue, 5 Feb 2019 16:27:28 -0500 [thread overview]
Message-ID: <631579E3-02F5-4E12-8BE6-DDAC0AE2E4A7@oracle.com> (raw)
In-Reply-To: <ACD02F93-6C71-4DEB-95B8-001F9AAD9E21@intel.com>
>
> Would poll work here instead?
Poll (or epoll) would definitely work - if we controlled the source and compilation of all the libraries that the application links against.
But an app doesn’t know how the libraries in the OS are implemented. We’d have no way to ensure select() isn’t called by a shared library - the first we would know is when the application randomly failed.
Seems pretty clear that the newer DPDK library is breaking the requirements of GNU libc to use less than 1024 file descriptors. The previous DPDK design was able to mmap the huge pages without requiring thousands of open file descriptors...
next prev parent reply other threads:[~2019-02-05 21:27 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-02-05 18:56 Iain Barker
2019-02-05 20:29 ` Wiles, Keith
2019-02-05 21:27 ` Iain Barker [this message]
2019-02-05 21:36 ` Wiles, Keith
2019-02-05 21:49 ` Iain Barker
2019-02-05 22:02 ` Wiles, Keith
2019-02-06 13:57 ` Iain Barker
2019-02-07 11:15 ` Burakov, Anatoly
2019-02-22 17:08 ` Burakov, Anatoly
2019-02-27 13:57 ` Iain Barker
2019-02-27 18:02 ` Edwin Leung
2019-02-28 10:36 ` Burakov, Anatoly
[not found] <1820650896.208393.1633616003335.ref@mail.yahoo.com>
2021-10-07 14:13 ` Vijay Atreya
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=631579E3-02F5-4E12-8BE6-DDAC0AE2E4A7@oracle.com \
--to=iain.barker@oracle.com \
--cc=dev@dpdk.org \
--cc=edwin.leung@oracle.com \
--cc=keith.wiles@intel.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).