From: Darren Hart <dvhart@linux.intel.com>
To: David Miller <davem@davemloft.net>
Cc: linux-kernel@vger.kernel.org, Darren Hart <dvhart@infradead.org>
Subject: Re: futex testsuite suggestion...
Date: Mon, 27 Oct 2014 13:29:14 -0700 [thread overview]
Message-ID: <544EAB1A.2030403@linux.intel.com> (raw)
In-Reply-To: <20141027.155656.1414383076601514662.davem@davemloft.net>
On 10/27/14 12:56, David Miller wrote:
>
> First of all, thanks so much for writing your futex test suite, it's
> proved invaluable for sparc64 kernel development for me lately.
Hi David,
Glad to hear it :-)
>
> I'd like to suggest that you add a test that triggers transparent
> hugepages, because if an architecture doesn't implement
> __get_user_pages_fast() such futexes cause a machine to hang.
>
> I hacked up something simple that took the existing performance
> test and made it operate in a register allocated using memalign().
>
> I would suggest doing a memalign(HUGEPAGE_SIZE, HUGEPAGE_SIZE) then
> iterating running a futex test within each normal page within that
> hugepage.
Do you want this option for the performance tests, or would a less
intensive functional test be sufficient?
The other thing to note is there have been several efforts/false starts
to get futextests into perf and kselftest. We currently considering
splitting futextests across the two (performance to perf, functional to
kselftest). The TODO for a fuzz tester is handled *more* than adequately
by trinity.
I'm perfectly happy to add such a test. I'm currently buried under a
number of other things that have resulted in futextests suffering
somewhat. So a couple of things to help make this happen:
1) Could you send me your hacked up test, in whatever condition?
2) I'm more than happy to accept patches, but I do understand why you
might prefer to have someone else write it :-)
Thanks,
--
Darren Hart
Intel Open Source Technology Center
next prev parent reply other threads:[~2014-10-27 20:29 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-10-27 19:56 futex testsuite suggestion David Miller
2014-10-27 20:29 ` Darren Hart [this message]
2014-10-27 20:31 ` David Miller
2014-11-22 8:02 ` Darren Hart
2014-11-24 22:07 ` David Miller
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=544EAB1A.2030403@linux.intel.com \
--to=dvhart@linux.intel.com \
--cc=davem@davemloft.net \
--cc=dvhart@infradead.org \
--cc=linux-kernel@vger.kernel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.