From: Nathan Zimmer <nzimmer@sgi.com>
To: linux-btrace@vger.kernel.org
Subject: Re: [PATCH 0/5] Improve scaling and hotplugging tolerance in blktrace and friends
Date: Tue, 30 Jul 2013 19:29:17 +0000 [thread overview]
Message-ID: <51F8140D.3000409@sgi.com> (raw)
In-Reply-To: <1366037616-20159-1-git-send-email-nzimmer@sgi.com>
On 04/16/2013 01:02 AM, Jens Axboe wrote:
> On Mon, Apr 15 2013, Nathan Zimmer wrote:
>> While looking for issues at 4096 cpus I noticed that blktrace was behaving
>> oddly. Upon reviewing I discovered some parts of the code were written at at
>> time when boxes were limited to 512 and holes in cpu maps were impossible.
>>
>> This patch series should correct that.
> Thanks Nathan. I reviewed all 5 and have applied them.
>
Have you pushed the patches lately?
I checked the public branch git://git.kernel.dk/blktrace.git and I
didn't see my changes.
Thanks,
Nate
next prev parent reply other threads:[~2013-07-30 19:29 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-04-15 14:53 [PATCH 0/5] Improve scaling and hotplugging tolerance in blktrace and friends Nathan Zimmer
2013-04-16 6:02 ` Jens Axboe
2013-07-30 19:29 ` Nathan Zimmer [this message]
2013-08-01 15:43 ` Jens Axboe
2013-08-01 18:11 ` Jens Axboe
2013-08-02 12:43 ` Nathan Zimmer
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=51F8140D.3000409@sgi.com \
--to=nzimmer@sgi.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).