public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Michel Lespinasse <walken@google.com>
To: Andrew Morton <akpm@linux-foundation.org>,
	David Howells <dhowells@redhat.com>
Cc: linux-kernel@vger.kernel.org, Rik van Riel <riel@redhat.com>
Subject: [PATCH 0/2] extend synchro-test module to test spinlocks too
Date: Sun, 30 Dec 2012 18:47:12 -0800	[thread overview]
Message-ID: <1356922034-25165-1-git-send-email-walken@google.com> (raw)

I wanted a synthetic test to help me understand the performance of Rik's
proposed spinlock proportional backoff patches, and the synchro-test
in andrew's mmotm tree looked like an obvious candidate to be extended,
so I ended up with the following couple patches.

I'm not sure whats' the back story with synchro-test though - they seem
to have been stuck in andrew's tree for a very long time now. Is there
any reason delaying their inclusion or is it just that nobody's been
pushing for them ?

Michel Lespinasse (2):
  add spinlock test to synchro-test module
  Document default load and interval values in synchro-test module

 Documentation/synchro-test.txt |    4 +-
 kernel/synchro-test.c          |   76 ++++++++++++++++++++++++++++++++++++---
 2 files changed, 72 insertions(+), 8 deletions(-)

-- 
1.7.7.3


             reply	other threads:[~2012-12-31  2:47 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-12-31  2:47 Michel Lespinasse [this message]
2012-12-31  2:47 ` [PATCH 1/2] add spinlock test to synchro-test module Michel Lespinasse
2012-12-31  2:47 ` [PATCH 2/2] Document default load and interval values in " Michel Lespinasse
2013-01-02 22:39 ` [PATCH 0/2] extend synchro-test module to test spinlocks too Andrew Morton
2013-02-03  3:22   ` Michel Lespinasse

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=1356922034-25165-1-git-send-email-walken@google.com \
    --to=walken@google.com \
    --cc=akpm@linux-foundation.org \
    --cc=dhowells@redhat.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=riel@redhat.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