linux-btrace.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Alan D. Brunelle" <Alan.Brunelle@hp.com>
To: Jens Axboe <jens.axboe@oracle.com>
Cc: "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	linux-btrace@vger.kernel.org
Subject: Re: [PATCH] Changed blk trace msgs to directly use relay buffer
Date: Wed, 28 May 2008 12:26:27 +0000	[thread overview]
Message-ID: <483D4F73.5020503@hp.com> (raw)
In-Reply-To: <20080528121329.GU25504@kernel.dk>

Jens Axboe wrote:
> On Tue, May 27 2008, Alan D. Brunelle wrote:
> 
>> From 43c8ea2b78f31d7ccd349384a9a2084e787aafc1 Mon Sep 17 00:00:00 2001
>> From: Alan D. Brunelle <alan.brunelle@hp.com>
>> Date: Tue, 27 May 2008 10:32:36 -0400
>> Subject: [PATCH] Changed blk trace msgs to directly use relay buffer
>>
>> Allows for SMP-usage without corruption, and removes an extra copy at
>> the expense of copying extra bytes. Reduced message size from 1024 to 128.
> 
> Or, alternatively, something like the below. Then we don't
> unconditionally reserve and copy 128 bytes for each message, at the
> cost 128 bytes per-cpu per trace.

I looked into something like this, but thought the added complexity
wasn't worth it. Besides the extra per-cpu stuff, you also have an extra
memcopy involved - in my patch you print directly into the relay buffer.
I figure that /if/ copying (128-msg_size) extra bytes is too much, one
could always shrink the 128 down further. [I would think 64 bytes is
probably ok.]

I'd bet that the reduced complexity, and skipping the extra memcopy more
than offsets having to copy a few extra bytes...

Alan

  reply	other threads:[~2008-05-28 12:26 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-05-27 14:36 [PATCH] Changed blk trace msgs to directly use relay buffer Alan D. Brunelle
2008-05-28 12:13 ` Jens Axboe
2008-05-28 12:26   ` Alan D. Brunelle [this message]
2008-05-28 13:00     ` Jens Axboe
2008-05-28 13:22       ` Alan D. Brunelle
2008-05-28 13:28         ` Jens Axboe

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=483D4F73.5020503@hp.com \
    --to=alan.brunelle@hp.com \
    --cc=jens.axboe@oracle.com \
    --cc=linux-btrace@vger.kernel.org \
    --cc=linux-kernel@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).