From: Jarkko Sakkinen <jarkko.sakkinen@linux.intel.com>
To: Jethro Beekman <jethro@fortanix.com>
Cc: Sean Christopherson <sean.j.christopherson@intel.com>,
"linux-sgx@vger.kernel.org" <linux-sgx@vger.kernel.org>
Subject: Re: Unable to load large enclave
Date: Wed, 7 Oct 2020 21:34:57 +0300 [thread overview]
Message-ID: <20201007183457.GA4850@linux.intel.com> (raw)
In-Reply-To: <f56d8b2c-36ce-0852-c1d4-5e1b41a491f7@fortanix.com>
On Wed, Oct 07, 2020 at 08:14:48PM +0200, Jethro Beekman wrote:
> It's this one in do_mmap():
>
> /* Too many mappings? */
> if (mm->map_count > sysctl_max_map_count)
> return -ENOMEM;
>
> I've verified that I'm no longer getting the problem when increasing
> /proc/sys/vm/max_map_count . Why do I need to change this from the
> default compared to before?
Yes, you are correct. I came into same conclusion and responded (once
again) to my own email after running this:
➜ ~ (master) ✔ sudo bpftrace -e 'kr:ksys_mmap_pgoff { @[comm] = count(); }' &> log.txt
^C
➜ ~ (master) ✔ cat log.txt
Attaching 1 probe...
@[cat]: 18
@[git]: 47
@[zsh]: 49
@[cargo]: 94
@[sgx-load-large-]: 65510
That is the default value for /proc/sys/vm/max_map_count.
Re-responding just in case because I thought that the bpftrace snippet
might have some value for you. I don't why I cannot see my email at
lore.kernel.org.
/Jarkko
next prev parent reply other threads:[~2020-10-07 19:40 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-29 15:52 Unable to load large enclave Jethro Beekman
2020-09-30 1:16 ` Jarkko Sakkinen
2020-09-30 7:12 ` Jethro Beekman
2020-09-30 11:45 ` Jarkko Sakkinen
2020-10-03 13:12 ` Jarkko Sakkinen
2020-10-05 22:56 ` Sean Christopherson
2020-10-06 15:13 ` Jarkko Sakkinen
2020-10-07 15:49 ` Jarkko Sakkinen
2020-10-07 16:13 ` Jethro Beekman
2020-10-07 17:20 ` Jarkko Sakkinen
2020-10-07 18:14 ` Jethro Beekman
2020-10-07 18:34 ` Jarkko Sakkinen [this message]
2020-10-07 18:36 ` Jarkko Sakkinen
2020-10-07 18:25 ` Jarkko Sakkinen
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=20201007183457.GA4850@linux.intel.com \
--to=jarkko.sakkinen@linux.intel.com \
--cc=jethro@fortanix.com \
--cc=linux-sgx@vger.kernel.org \
--cc=sean.j.christopherson@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 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.