From: Andrew Morton <akpm@linux-foundation.org>
To: Jason Baron <jbaron@redhat.com>
Cc: davidel@xmailserver.org, nelhage@ksplice.com,
torvalds@linux-foundation.org, linux-kernel@vger.kernel.org,
Steven Rostedt <rostedt@goodmis.org>
Subject: Re: [PATCH RFC] epoll: limit paths
Date: Tue, 6 Sep 2011 12:45:07 -0700 [thread overview]
Message-ID: <20110906124507.b62d8158.akpm@linux-foundation.org> (raw)
In-Reply-To: <20110906133640.GA6163@redhat.com>
On Tue, 6 Sep 2011 09:36:41 -0400
Jason Baron <jbaron@redhat.com> wrote:
> > I don't think we have any maintained public test code for epoll? And I
> > trust you have some? It would be good if you could merge whatever you
> > have into the main kernel. Then each time we fix bugs or add features,
> > I can harrass people to update the test harness to track the changes.
> >
>
> ok. The tests I've used to test this were:
>
> -pipetest.c: http://www.gelato.unsw.edu.au/archives/linux-ia64/0405/9684.html
> -test I posted in https://lkml.org/lkml/2011/2/25/297
> -test Nelson posted in https://lkml.org/lkml/2011/2/25/297
> -some variations on the above tests
>
> I can clean these up, and try and propose them for merge...also where would
> they live?
We don't have a formal self-test framework in-kernel. Probably much
chin-scratching would precede such a thing. For now I guess you could
follow Steve and use tools/testing/epoll/.
Perhaps you might go as far as to permit one to type "cd tools/testing
; make test" and have it run all the self-tests. Which will consist of
epoll ;)
prev parent reply other threads:[~2011-09-06 19:45 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-09-02 18:59 [PATCH RFC] epoll: limit paths Jason Baron
2011-09-02 21:49 ` Andrew Morton
2011-09-06 13:36 ` Jason Baron
2011-09-06 19:45 ` Andrew Morton [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=20110906124507.b62d8158.akpm@linux-foundation.org \
--to=akpm@linux-foundation.org \
--cc=davidel@xmailserver.org \
--cc=jbaron@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=nelhage@ksplice.com \
--cc=rostedt@goodmis.org \
--cc=torvalds@linux-foundation.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;
as well as URLs for NNTP newsgroup(s).