From: Dennis Zhou <dennis@kernel.org>
To: Eddie Hao <eddieh@google.com>,
Vlad Dumitrescu <vladum@google.com>,
Willem de Bruijn <willemb@google.com>
Cc: Alexei Starovoitov <ast@kernel.org>, Tejun Heo <tj@kernel.org>,
Christoph Lameter <cl@linux.com>,
linux-mm@kvack.org, linux-kernel@vger.kernel.org
Subject: LPC Traffic Shaping w/ BPF Talk - percpu followup
Date: Tue, 20 Nov 2018 17:16:59 -0500 [thread overview]
Message-ID: <20181120221659.GA61322@dennisz-mbp.dhcp.thefacebook.com> (raw)
Hi Eddie, Vlad, and Willem,
A few people mentioned to me that you guys were experiencing issues with
the percpu memory allocator. I saw the talk slides mention the
following two bullets:
1) allocation pattern makes the per cpu allocator reach a highly
fragmented state
2) sometimes takes a long time (up to 12s) to create the PERCPU_HASH
maps at startup
Could you guys elaborate a little more about the above? Some things
that would help: kernel version, cpu info, and a reproducer if possible?
Also, I did some work last summer to make percpu allocation more
efficient, which went into the 4.14 kernel. Just to be sure, is that a
part of the kernel you guys are running?
Thanks,
Dennis
next reply other threads:[~2018-11-20 22:17 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-11-20 22:16 Dennis Zhou [this message]
2018-11-22 4:01 ` Vlad Dumitrescu
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=20181120221659.GA61322@dennisz-mbp.dhcp.thefacebook.com \
--to=dennis@kernel.org \
--cc=ast@kernel.org \
--cc=cl@linux.com \
--cc=eddieh@google.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=tj@kernel.org \
--cc=vladum@google.com \
--cc=willemb@google.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