From: Markus Elfring <Markus.Elfring@web.de>
To: "Ian Rogers" <irogers@google.com>,
linux-perf-users@vger.kernel.org,
"Adrian Hunter" <adrian.hunter@intel.com>,
"Alexander Shishkin" <alexander.shishkin@linux.intel.com>,
"Anne Macedo" <retpolanne@posteo.net>,
"Arnaldo Carvalho de Melo" <acme@kernel.org>,
"Dominique Martinet" <asmadeus@codewreck.org>,
"Ingo Molnar" <mingo@redhat.com>,
"James Clark" <james.clark@linaro.org>,
"Jean-Philippe Romain" <jean-philippe.romain@foss.st.com>,
"Jesper Juhl" <jesperjuhl76@gmail.com>,
"Jiri Olsa" <jolsa@kernel.org>,
"Junhao He" <hejunhao3@huawei.com>,
"Kan Liang" <kan.liang@linux.intel.com>,
"Krzysztof Łopatowski" <krzysztof.m.lopatowski@gmail.com>,
"Mark Rutland" <mark.rutland@arm.com>,
"Michael Petlan" <mpetlan@redhat.com>,
"Namhyung Kim" <namhyung@kernel.org>,
"Peter Zijlstra" <peterz@infradead.org>,
"Sam James" <sam@gentoo.org>,
"Thomas Richter" <tmricht@linux.ibm.com>,
"Veronika Molnarova" <vmolnaro@redhat.com>,
"Yicong Yang" <yangyicong@hisilicon.com>,
"Zhongqiu Han" <quic_zhonhan@quicinc.com>
Cc: LKML <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH v2 1/7] tools lib api: Add io_dir() as an allocation free readdir() alternative
Date: Sat, 8 Feb 2025 18:02:48 +0100 [thread overview]
Message-ID: <af27ddaa-ca9f-4796-bf33-574a39f9f5d7@web.de> (raw)
In-Reply-To: <20250207232452.994822-2-irogers@google.com>
…
> syscall use was made uncondtional to work around this. …
unconditional?
Regards,
Markus
next prev parent reply other threads:[~2025-02-08 17:04 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-02-07 23:24 [PATCH v2 0/7] Add io_dir to avoid memory overhead from opendir Ian Rogers
2025-02-07 23:24 ` [PATCH v2 1/7] tools lib api: Add io_dir an allocation free readdir alternative Ian Rogers
2025-02-08 17:02 ` Markus Elfring [this message]
2025-02-19 21:51 ` Namhyung Kim
2025-02-19 22:21 ` Ian Rogers
2025-02-21 6:31 ` Namhyung Kim
2025-02-07 23:24 ` [PATCH v2 2/7] perf maps: Switch modules tree walk to io_dir__readdir Ian Rogers
2025-02-07 23:24 ` [PATCH v2 3/7] perf pmu: Switch " Ian Rogers
2025-02-07 23:24 ` [PATCH v2 4/7] perf header: Switch mem topology " Ian Rogers
2025-02-07 23:24 ` [PATCH v2 5/7] perf events: Remove scandir in thread synthesis Ian Rogers
2025-02-07 23:24 ` [PATCH v2 6/7] perf parse-events: Switch tracepoints to io_dir__readdir Ian Rogers
2025-02-07 23:24 ` [PATCH v2 7/7] perf hwmon_pmu: Switch event discovery " Ian Rogers
2025-02-08 10:58 ` [PATCH v2 0/7] Add io_dir to avoid memory overhead from opendir David Laight
2025-02-08 12:15 ` Ian Rogers
2025-02-19 21:54 ` Namhyung Kim
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=af27ddaa-ca9f-4796-bf33-574a39f9f5d7@web.de \
--to=markus.elfring@web.de \
--cc=acme@kernel.org \
--cc=adrian.hunter@intel.com \
--cc=alexander.shishkin@linux.intel.com \
--cc=asmadeus@codewreck.org \
--cc=hejunhao3@huawei.com \
--cc=irogers@google.com \
--cc=james.clark@linaro.org \
--cc=jean-philippe.romain@foss.st.com \
--cc=jesperjuhl76@gmail.com \
--cc=jolsa@kernel.org \
--cc=kan.liang@linux.intel.com \
--cc=krzysztof.m.lopatowski@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-perf-users@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=mingo@redhat.com \
--cc=mpetlan@redhat.com \
--cc=namhyung@kernel.org \
--cc=peterz@infradead.org \
--cc=quic_zhonhan@quicinc.com \
--cc=retpolanne@posteo.net \
--cc=sam@gentoo.org \
--cc=tmricht@linux.ibm.com \
--cc=vmolnaro@redhat.com \
--cc=yangyicong@hisilicon.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).