All of lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Monjalon <thomas@monjalon.net>
To: Anatoly Burakov <anatoly.burakov@intel.com>
Cc: dev@dpdk.org, John McNamara <john.mcnamara@intel.com>,
	Marko Kovacevic <marko.kovacevic@intel.com>,
	david.marchand@redhat.com, maxime.coquelin@redhat.com
Subject: Re: [PATCH v2 2/2] memalloc: do not use lockfiles for single file segments mode
Date: Tue, 02 Apr 2019 16:08:24 +0200	[thread overview]
Message-ID: <4936199.LOJ53TdX45@xps> (raw)
In-Reply-To: <2b5404285e5ddc460a857cc90130db1b2c717dfc.1553882085.git.anatoly.burakov@intel.com>

29/03/2019 18:55, Anatoly Burakov:
> 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.
> 
> Single file segments option stores lock files per page to ensure
> that pages are deleted when there are no more users, however this
> is not necessary because the processes will be holding onto the
> pages anyway because of mmap(). Thus, removing pages from the
> filesystem is safe even though they may be used by some other
> secondary process. As a result, single file segments mode no
> longer stores inordinate amounts of segment fd's, and the above
> issue with fd limits is solved.
> 
> However, this will not work for legacy mem mode. For that, simply
> document that using bigger page sizes is the only option.
> 
> [1] https://mails.dpdk.org/archives/dev/2019-February/124386.html
> 
> Signed-off-by: Anatoly Burakov <anatoly.burakov@intel.com>

Applied, thanks

      reply	other threads:[~2019-04-02 14:08 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-02-22 17:12 [PATCH] eal: add option to not store segment fd's Anatoly Burakov
2019-03-29  9:50 ` David Marchand
2019-03-29 10:33   ` Burakov, Anatoly
2019-03-29 11:34     ` Thomas Monjalon
2019-03-29 12:05       ` Burakov, Anatoly
2019-03-29 12:40         ` Thomas Monjalon
2019-03-29 13:24           ` Burakov, Anatoly
2019-03-29 13:34             ` Thomas Monjalon
2019-03-29 14:21               ` Burakov, Anatoly
2019-03-29 13:35             ` Maxime Coquelin
2019-03-29 17:55 ` [PATCH v2 1/2] memalloc: refactor segment resizing code Anatoly Burakov
2019-03-29 17:55 ` [PATCH v2 2/2] memalloc: do not use lockfiles for single file segments mode Anatoly Burakov
2019-04-02 14:08   ` Thomas Monjalon [this message]

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=4936199.LOJ53TdX45@xps \
    --to=thomas@monjalon.net \
    --cc=anatoly.burakov@intel.com \
    --cc=david.marchand@redhat.com \
    --cc=dev@dpdk.org \
    --cc=john.mcnamara@intel.com \
    --cc=marko.kovacevic@intel.com \
    --cc=maxime.coquelin@redhat.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.