From: Dave Jones <davej@redhat.com>
To: trinity@vger.kernel.org
Subject: Fwd: Trinity 1.4 tarball release.
Date: Mon, 12 May 2014 13:43:32 -0400 [thread overview]
Message-ID: <20140512174332.GA3345@redhat.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 116 bytes --]
heh, I knew I'd forget something. Hopefully "cc'ing the trinity list"
was the only thing this time around..
Dave
[-- Attachment #2: Type: message/rfc822, Size: 1439 bytes --]
From: Dave Jones <davej@redhat.com>
To: Linux Kernel <linux-kernel@vger.kernel.org>
Cc: linux-mm@kvack.org
Subject: Trinity 1.4 tarball release.
Date: Mon, 12 May 2014 13:14:09 -0400
Message-ID: <20140512171409.GA32653@redhat.com>
I finally got around to cutting a new release of trinity, hopefully
putting off the "are you running git, or tarball?" questions for a while.
Big changes since 1.3 include some more targetted fuzzing of VM related
syscalls, which judging from the fallout over the last six months, seems
to be working quite well.
Trinity should now also scale up a lot better on bigger machines with lots of cores.
It should pick a reasonable default number of child processes, but you
can override with -C as you could before, but now without any restrictions other
than available memory. (I'd love to hear stories of people running it
on some of the more extreme systems, especially if something interesting broke)
Info, tarballs, and pointers to git are as always, at
http://codemonkey.org.uk/projects/trinity/
thanks to everyone who sent patches, chased down interesting kernel bugs
trinity found, or who gave me ideas/feedback. Your input has been much
appreciated.
Dave
next reply other threads:[~2014-05-12 17:43 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-05-12 17:43 Dave Jones [this message]
2014-05-13 6:43 ` Fwd: Trinity 1.4 tarball release Michael Ellerman
2014-05-13 14:00 ` Dave Jones
2014-05-14 7:26 ` Michael Ellerman
2014-05-14 13:35 ` Dave Jones
2014-05-22 2:40 ` Michael Ellerman
2014-05-22 3:40 ` Dave Jones
2014-05-22 3:43 ` Michael Ellerman
2014-05-22 3:41 ` Michael Ellerman
2014-05-22 3:50 ` Dave Jones
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=20140512174332.GA3345@redhat.com \
--to=davej@redhat.com \
--cc=trinity@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 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 read-only IMAP folder(s) and NNTP newsgroup(s).