From: Namhyung Kim <namhyung@kernel.org>
To: Ian Rogers <irogers@google.com>,
Arnaldo Carvalho de Melo <acme@kernel.org>,
Peter Zijlstra <peterz@infradead.org>,
Oliver Upton <oliver.upton@linux.dev>,
Adrian Hunter <adrian.hunter@intel.com>,
Yang Jihong <yangjihong1@huawei.com>,
linux-perf-users@vger.kernel.org, Ingo Molnar <mingo@redhat.com>,
Jiri Olsa <jolsa@kernel.org>, Mark Rutland <mark.rutland@arm.com>,
linux-kernel@vger.kernel.org,
Alexander Shishkin <alexander.shishkin@linux.intel.com>
Subject: Re: [PATCH v4 0/7] Thread memory improvements and fixes
Date: Mon, 4 Mar 2024 10:57:12 -0800 [thread overview]
Message-ID: <170957856865.1606352.14840215772677591593.b4-ty@kernel.org> (raw)
In-Reply-To: <20240301053646.1449657-1-irogers@google.com>
On Thu, 29 Feb 2024 21:36:38 -0800, Ian Rogers wrote:
> The next 6 patches (now 7) from:
> https://lore.kernel.org/lkml/20240202061532.1939474-1-irogers@google.com/
> now the initial maps fixes have landed:
> https://lore.kernel.org/all/20240210031746.4057262-1-irogers@google.com/
>
> Separate out and reimplement threads to use a hashmap for lower memory
> consumption and faster look up. The fixes a regression in memory usage
> where reference count checking switched to using non-invasive tree
> nodes. Reduce threads default size by 32 times and improve locking
> discipline. Also, fix regressions where tids had become unordered to
> make `perf report --tasks` and `perf trace --summary` output easier to
> read.
>
> [...]
Applied to perf-tools-next, thanks!
Best regards,
--
Namhyung Kim <namhyung@kernel.org>
prev parent reply other threads:[~2024-03-04 18:57 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-01 5:36 Ian Rogers
2024-03-01 5:36 ` [PATCH v4 1/7] perf report: Sort child tasks by tid Ian Rogers
2024-03-01 5:36 ` [PATCH v4 2/7] perf trace: Ignore thread hashing in summary Ian Rogers
2024-03-01 5:36 ` [PATCH v4 3/7] perf machine: Move fprintf to for_each loop and a callback Ian Rogers
2024-03-01 5:36 ` [PATCH v4 4/7] perf machine: Move machine's threads into its own abstraction Ian Rogers
2024-03-01 5:36 ` [PATCH v4 5/7] perf threads: Move threads to its own files Ian Rogers
2024-03-01 5:36 ` [PATCH v4 6/7] perf threads: Switch from rbtree to hashmap Ian Rogers
2024-03-01 5:36 ` [PATCH v4 7/7] perf threads: Reduce table size from 256 to 8 Ian Rogers
2024-03-04 6:45 ` [PATCH v4 0/7] Thread memory improvements and fixes Namhyung Kim
2024-03-04 18:57 ` Namhyung Kim [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=170957856865.1606352.14840215772677591593.b4-ty@kernel.org \
--to=namhyung@kernel.org \
--cc=acme@kernel.org \
--cc=adrian.hunter@intel.com \
--cc=alexander.shishkin@linux.intel.com \
--cc=irogers@google.com \
--cc=jolsa@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-perf-users@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=mingo@redhat.com \
--cc=oliver.upton@linux.dev \
--cc=peterz@infradead.org \
--cc=yangjihong1@huawei.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
all inboxes | Powered by JetHome®