From: "Alan D. Brunelle" <Alan.Brunelle@hp.com>
To: linux-btrace@vger.kernel.org
Subject: Updates today...
Date: Wed, 11 Feb 2009 19:22:11 +0000 [thread overview]
Message-ID: <49932563.1090708@hp.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 390 bytes --]
I've updated blktrace w/ the following commits. It has enabled me to
handle a moderate load on a 32-way ia64 box w/ 88 disks being used. (The
load is to build an Oracle database w/ 5000 warehouses onto the volume
constructed from those 88 disks.) I used both local & networked modes,
and had _zero_ drops over a 400 second period. (The load was generating
about 44,500 traces per second.)
[-- Attachment #2: x --]
[-- Type: text/plain, Size: 1513 bytes --]
commit e6855475478967e7cf92f8beece05ea55d31e6f1
Author: Alan D. Brunelle <alan.brunelle@hp.com>
Date: Wed Feb 11 13:40:09 2009 -0500
btt: fixed open in setup_ifile
Took my_open & my_fopen code from blktrace 2.0: needed to add in open
resource limit increasing stuff.
Signed-off-by: Alan D. Brunelle <alan.brunelle@hp.com>
commit 6488ca487c5695b784db56c79b67007e92eeb2ac
Author: Alan D. Brunelle <alan.brunelle@hp.com>
Date: Wed Feb 11 13:23:21 2009 -0500
Synchronized trace gathering
Previously, each tracer thread would start gathering traces as soon as
it got going - which might slow down later thread start ups. This change
allows each thread to be ready to gather traces, and then the main
thread starts all the threads gathering at the same time.
commit e58f3937548ed115ac5104817f2a9df53830f381
Author: Alan D. Brunelle <alan.brunelle@hp.com>
Date: Wed Feb 11 13:10:13 2009 -0500
Invoke gethostbyname once, handle errors better
Instead of invoking gethostbyname once per client, we only need to do it
once at initialization time. Plus: gethostbyname has a non-standard
errno reporting mechanism, handle this better.
commit d5302b03b2728a27f14c4f260ce6a5247ea87c6e
Author: Alan D. Brunelle <alan.brunelle@hp.com>
Date: Wed Feb 11 11:42:09 2009 -0500
Added accept as a system call needing resource increases
accept(2) opens a socket, and thus needs to handle EMFILE/ENFILE errors
like other system calls.
reply other threads:[~2009-02-11 19:22 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=49932563.1090708@hp.com \
--to=alan.brunelle@hp.com \
--cc=linux-btrace@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 NNTP newsgroup(s).