From: Ingo Molnar <mingo@kernel.org>
To: Yuanhan Liu <yuanhan.liu@linux.intel.com>
Cc: Michel Lespinasse <walken@google.com>,
linux-kernel@vger.kernel.org, David Howells <dhowells@redhat.com>
Subject: Re: [PATCH] rwsem-spinlock: let rwsem write lock stealable
Date: Thu, 31 Jan 2013 22:18:18 +0100 [thread overview]
Message-ID: <20130131211818.GA13195@gmail.com> (raw)
In-Reply-To: <20130131143626.GB12678@yliu-dev.sh.intel.com>
[-- Attachment #1: Type: text/plain, Size: 1172 bytes --]
* Yuanhan Liu <yuanhan.liu@linux.intel.com> wrote:
> On Thu, Jan 31, 2013 at 02:12:28PM +0100, Ingo Molnar wrote:
> >
> > * Yuanhan Liu <yuanhan.liu@linux.intel.com> wrote:
> >
> > > BTW, mind to tell a nice test case for mmap_sem?
> >
> > this one was write-hitting on mmap_sem pretty hard, last I
> > checked:
> >
> > http://people.redhat.com/mingo/threaded-mmap-stresstest/
>
> Thanks!
>
> Is there any pass condition? I tested a while, at least I
> found no oops or any noisy from dmesg output. Is that OK?
Yeah, not crashing and not hanging is the expected behavior.
> Well, sometimes, it will quit peacefully. Sometimes it will
> not. ps -eo 'pid, state,wchan,comm' shows that it is sleeping
> at futex_wait_queue_me().
>
> NOTE: this happens both with or w/o this patch. Thus it may
> not an issue introduced by this patch?
hm, that's unexpected - it's expected to loop infinitely. I have
a newer version (attached) - is that exiting too?
Maybe this triggers spuriously:
if (!info->si_addr)
raise(SIGABRT); /* Allow GDB backtrace */
although then you should see the SIGABRT as an irregular exit
IIRC.
Thanks,
Ingo
[-- Attachment #2: threaded-mmap-stresstest.tar.gz --]
[-- Type: application/x-gzip, Size: 3036 bytes --]
next prev parent reply other threads:[~2013-01-31 21:18 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-01-30 9:14 [PATCH] rwsem-spinlock: let rwsem write lock stealable Yuanhan Liu
2013-01-31 9:39 ` Ingo Molnar
2013-01-31 10:09 ` Yuanhan Liu
2013-01-31 10:45 ` Ingo Molnar
2013-01-31 12:23 ` Yuanhan Liu
2013-01-31 11:57 ` Michel Lespinasse
2013-01-31 12:40 ` Yuanhan Liu
2013-01-31 13:12 ` Ingo Molnar
2013-01-31 14:36 ` Yuanhan Liu
2013-01-31 21:18 ` Ingo Molnar [this message]
2013-02-01 2:16 ` Yuanhan Liu
2013-01-31 13:10 ` Ingo Molnar
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=20130131211818.GA13195@gmail.com \
--to=mingo@kernel.org \
--cc=dhowells@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=walken@google.com \
--cc=yuanhan.liu@linux.intel.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