DPDK patches and discussions
 help / color / mirror / Atom feed
From: "Wiles, Keith" <keith.wiles@intel.com>
To: Iain Barker <iain.barker@oracle.com>
Cc: "dev@dpdk.org" <dev@dpdk.org>,
	"edwin.leung@oracle.com" <edwin.leung@oracle.com>,
	"Burakov, Anatoly" <anatoly.burakov@intel.com>
Subject: Re: [dpdk-dev] Question about DPDK hugepage fd change
Date: Tue, 5 Feb 2019 22:02:34 +0000	[thread overview]
Message-ID: <896AF59A-4CCF-42FE-B2D7-160C69427DD2@intel.com> (raw)
In-Reply-To: <345EDE69-C416-405F-B88C-04EE8384D20F@oracle.com>



> On Feb 5, 2019, at 3:49 PM, Iain Barker <iain.barker@oracle.com> wrote:
> 
> 
>> 
>> Maybe I do not see the full problem here. If DPDK used poll instead of select it would solve the 1024 problem as poll has a high limit to the number of file descriptors at least that was my assumption. 
>>> 
> 
> Thanks Keith. 
> 
> The issue is not whether DPDK is using poll or select on the fd’s.
> 
> The issue is that DPDK is raising the per-process number of fd’s above the maximum that glibc supports for select(). 
> 
> Therefore no other code within that process can reliably use select() on an fd set, because any file that is opened may get an fd number > 1024.

I see now. Then it means the application must also use poll or we have to release these fd’s after used to free up some fd’s below 1024 (which I assume is not possible) or something else needs to happen. These are questions for Anatoly I guess.

Can you use 1G hugepages instead of 2M pages or a combo of the two, not sure how dpdk handles having both in the system?
> 

Regards,
Keith


  reply	other threads:[~2019-02-05 22:02 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
2019-02-05 21:36     ` Wiles, Keith
2019-02-05 21:49       ` Iain Barker
2019-02-05 22:02         ` Wiles, Keith [this message]
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=896AF59A-4CCF-42FE-B2D7-160C69427DD2@intel.com \
    --to=keith.wiles@intel.com \
    --cc=anatoly.burakov@intel.com \
    --cc=dev@dpdk.org \
    --cc=edwin.leung@oracle.com \
    --cc=iain.barker@oracle.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).