From: Takuya Yoshikawa <takuya.yoshikawa@gmail.com>
To: Ingo Molnar <mingo@kernel.org>
Cc: Peter Zijlstra <peterz@infradead.org>,
linux-kernel@vger.kernel.org, linux-fsdevel@vger.kernel.org,
kvm@vger.kernel.org, avi@redhat.com, mtosatti@redhat.com,
yoshikawa.takuya@oss.ntt.co.jp
Subject: Re: [RFC] sched: make callers check lock contention for cond_resched_lock()
Date: Sat, 19 May 2012 01:10:01 +0900 [thread overview]
Message-ID: <20120519011001.521acd09c636f97e38f000d6@gmail.com> (raw)
In-Reply-To: <20120518072604.GG429@gmail.com>
On Fri, 18 May 2012 09:26:05 +0200
Ingo Molnar <mingo@kernel.org> wrote:
> I'm not sure we had a usable spin_is_contended() back then, nor
> was the !PREEMPT case in my mind really.
The fact that both spin_needbreak() and spin_is_contended() can be
used outside of sched is a bit confusing.
For example, in mm/compaction.c we are using spin_is_contended(), but
in mm/memory.c spin_needbreak().
BTW, the actual users of spin_is_contended() look to be only:
mm/compaction.c
security/keys/gc.c
> ( The patch looks ugly though, in 99% of the lines it just does
> something that cond_resched_lock() itself could do. )
Please ignore the patch. I have already found a way to solve my
problem without cond_resched().
Thanks,
Takuya
next prev parent reply other threads:[~2012-05-18 16:10 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-05-03 8:12 [RFC] sched: make callers check lock contention for cond_resched_lock() Takuya Yoshikawa
2012-05-03 8:35 ` Peter Zijlstra
2012-05-03 12:22 ` Takuya Yoshikawa
2012-05-03 12:29 ` Peter Zijlstra
2012-05-03 12:47 ` Avi Kivity
2012-05-03 14:11 ` Takuya Yoshikawa
2012-05-03 14:27 ` Avi Kivity
2012-05-03 14:38 ` Avi Kivity
2012-05-03 13:00 ` Takuya Yoshikawa
2012-05-03 15:47 ` Peter Zijlstra
2012-05-10 22:03 ` Takuya Yoshikawa
2012-05-18 7:26 ` Ingo Molnar
2012-05-18 16:10 ` Takuya Yoshikawa [this message]
2012-05-04 2:43 ` Michael Wang
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=20120519011001.521acd09c636f97e38f000d6@gmail.com \
--to=takuya.yoshikawa@gmail.com \
--cc=avi@redhat.com \
--cc=kvm@vger.kernel.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@kernel.org \
--cc=mtosatti@redhat.com \
--cc=peterz@infradead.org \
--cc=yoshikawa.takuya@oss.ntt.co.jp \
/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).