From: Steven Rostedt <rostedt@goodmis.org>
To: Waiman Long <longman@redhat.com>
Cc: Ingo Molnar <mingo@redhat.com>,
Peter Zijlstra <peterz@infradead.org>,
Juri Lelli <juri.lelli@redhat.com>,
Vincent Guittot <vincent.guittot@linaro.org>,
Dietmar Eggemann <dietmar.eggemann@arm.com>,
Ben Segall <bsegall@google.com>, Mel Gorman <mgorman@suse.de>,
Daniel Bristot de Oliveira <bristot@redhat.com>,
Bharata B Rao <bharata@linux.vnet.ibm.com>,
Phil Auld <pauld@redhat.com>,
Daniel Thompson <daniel.thompson@linaro.org>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v3] sched/debug: Use sched_debug_lock to serialize use of cgroup_path[] only
Date: Mon, 5 Apr 2021 11:59:18 -0400 [thread overview]
Message-ID: <20210405115918.702a2f8b@gandalf.local.home> (raw)
In-Reply-To: <4014fe97-5875-f64a-7b68-854a2b08394e@redhat.com>
On Sun, 4 Apr 2021 21:27:00 -0400
Waiman Long <longman@redhat.com> wrote:
> Thanks for the suggestion, but it also sound complicated.
It's not that complicated. Similar tricks have been used elsewhere in the
kernel.
>
> I think we can fix this lockup problem if we are willing to lose some
It's not a lockup problem, it's just a delay.
> information in case of contention. As you have suggested, a trylock will
> be used to acquire sched_debug_lock. If succeeded, all is good.
> Otherwise, a shorter stack buffer will be used for cgroup path. The path
> may be truncated in this case. If we detect that the full length of the
> buffer is used, we assume truncation and add, e.g. "...", to indicate
> there is more to the actual path.
>
> Do you think this is an acceptable comprise?
I guess that needs to be decided by those that use this information.
-- Steve
prev parent reply other threads:[~2021-04-05 15:59 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-04-01 18:10 Waiman Long
2021-04-02 20:40 ` Steven Rostedt
2021-04-03 3:09 ` Waiman Long
2021-04-04 16:02 ` Steven Rostedt
2021-04-05 1:27 ` Waiman Long
2021-04-05 1:29 ` Waiman Long
2021-04-05 15:59 ` Steven Rostedt [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=20210405115918.702a2f8b@gandalf.local.home \
--to=rostedt@goodmis.org \
--cc=bharata@linux.vnet.ibm.com \
--cc=bristot@redhat.com \
--cc=bsegall@google.com \
--cc=daniel.thompson@linaro.org \
--cc=dietmar.eggemann@arm.com \
--cc=juri.lelli@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=longman@redhat.com \
--cc=mgorman@suse.de \
--cc=mingo@redhat.com \
--cc=pauld@redhat.com \
--cc=peterz@infradead.org \
--cc=vincent.guittot@linaro.org \
/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®