From mboxrd@z Thu Jan 1 00:00:00 1970 From: "Alan D. Brunelle" Date: Wed, 28 May 2008 12:26:27 +0000 Subject: Re: [PATCH] Changed blk trace msgs to directly use relay buffer Message-Id: <483D4F73.5020503@hp.com> List-Id: References: <483C1C5A.5000001@hp.com> <20080528121329.GU25504@kernel.dk> In-Reply-To: <20080528121329.GU25504@kernel.dk> MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit To: Jens Axboe Cc: "linux-kernel@vger.kernel.org" , linux-btrace@vger.kernel.org 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 >> 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