[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <4CCEC1E6.9010806@kernel.dk>
Date: Mon, 01 Nov 2010 09:34:30 -0400
From: Jens Axboe <axboe@...nel.dk>
To: Mathieu Desnoyers <mathieu.desnoyers@...ymtl.ca>
CC: Jesper Juhl <jj@...osbits.net>, linux-kernel@...r.kernel.org,
Andrew Morton <akpm@...ux-foundation.org>,
Tom Zanussi <zanussi@...ibm.com>,
Karim Yaghmour <karim@...rsys.com>,
Paul Mundt <lethal@...ux-sh.org>,
Steven Rostedt <rostedt@...dmis.org>
Subject: Re: [PATCH] Optimize relay_alloc_page_array() slightly by using
vzalloc rather than vmalloc and memset
On 2010-11-01 09:08, Mathieu Desnoyers wrote:
> * Jens Axboe (axboe@...nel.dk) wrote:
>> On 2010-10-30 17:47, Mathieu Desnoyers wrote:
>>> BLK_DEV_IO_TRACE seems to still select RELAY. Has it completed its
>>> transition to either Ftrace or Perf ? Depending on Jens, moving blktrace
>>> relay dependency to the Generic Ring Buffer Library might be a good
>>> option to consider.
>>
>> The blktrace user bits is still (by far) the most wide spread way that
>> blktrace is used in the field, and those still rely on relayfs. So no,
>> we can't kill it now.
>
> What I am proposing is that the Generic Ring Buffer Library could
> replace relayfs without changing any of the interfaces blktrace exposes
> to user-space. Indeed, I would not remove relayfs unless there was a
> replacement.
Sure, I'm open to such a solution as long as it doesn't slow anything
down for blktrace (primary concern, certainly) and retains feature
parity. I'm not married to relayfs, it's just what was available easily
when I added blktrace originally.
--
Jens Axboe
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists