From: Jens Axboe <axboe@kernel.dk>
To: linux-btrace@vger.kernel.org
Subject: Re: [PATCH 0/5] Improve scaling and hotplugging tolerance in blktrace and friends
Date: Thu, 01 Aug 2013 18:11:09 +0000 [thread overview]
Message-ID: <20130801181109.GH24569@kernel.dk> (raw)
In-Reply-To: <1366037616-20159-1-git-send-email-nzimmer@sgi.com>
On Thu, Aug 01 2013, Jens Axboe wrote:
> On 07/30/2013 01:29 PM, Nathan Zimmer wrote:
> > 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.
>
> I wonder if I applied and forgot to push them out. Unfortunately my
> workstation is in transit at the moment. But I can just re-apply here
> and get it pushed out, sorry about that.
Doesn't work so well for me:
gcc -Wall -W -O2 -g -I. -I.. -I../btt -D_GNU_SOURCE -D_LARGEFILE_SOURCE
-D_FILE_OFFSET_BITSd -UCOUNT_IOS -UDEBUG -DNDEBUG -c -o btreplay.o
btreplay.c
btreplay.c: In function ‘pin_to_cpu’:
btreplay.c:554:2: error: request for member ‘__bits’ in something not a
structure or union
CPU_SET_S(tip->cpu, size, &cpus);
This should do it:
- CPU_ZERO_S(ncpus, &cpus);
- CPU_SET_S(tip->cpu, size, &cpus);
+ CPU_ZERO_S(ncpus, cpus);
+ CPU_SET_S(tip->cpu, size, cpus);
--
Jens Axboe
next prev parent reply other threads:[~2013-08-01 18:11 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
2013-08-01 15:43 ` Jens Axboe
2013-08-01 18:11 ` Jens Axboe [this message]
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=20130801181109.GH24569@kernel.dk \
--to=axboe@kernel.dk \
--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 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.