public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Jens Axboe <axboe@kernel.dk>
To: Mathieu Desnoyers <mathieu.desnoyers@polymtl.ca>
Cc: Jesper Juhl <jj@chaosbits.net>,
	linux-kernel@vger.kernel.org,
	Andrew Morton <akpm@linux-foundation.org>,
	Tom Zanussi <zanussi@us.ibm.com>,
	Karim Yaghmour <karim@opersys.com>,
	Paul Mundt <lethal@linux-sh.org>,
	Steven Rostedt <rostedt@goodmis.org>
Subject: Re: [PATCH] Optimize relay_alloc_page_array() slightly by using  vzalloc rather than vmalloc and memset
Date: Mon, 01 Nov 2010 09:34:30 -0400	[thread overview]
Message-ID: <4CCEC1E6.9010806@kernel.dk> (raw)
In-Reply-To: <20101101130842.GA24605@Krystal>

On 2010-11-01 09:08, Mathieu Desnoyers wrote:
> * Jens Axboe (axboe@kernel.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


  reply	other threads:[~2010-11-01 13:34 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-10-30 20:26 [PATCH] Optimize relay_alloc_page_array() slightly by using vzalloc rather than vmalloc and memset Jesper Juhl
2010-10-30 21:47 ` Mathieu Desnoyers
2010-10-30 21:50   ` Jesper Juhl
2010-10-31 18:39     ` Mathieu Desnoyers
2010-11-01  0:46       ` Andrew Morton
2010-11-01  6:58         ` Pekka Enberg
2010-11-01 11:27         ` Mathieu Desnoyers
2010-11-01 12:26           ` Américo Wang
2010-11-01 13:38         ` Mathieu Desnoyers
2010-11-01 12:22       ` Américo Wang
2010-11-01 13:00         ` el es
2010-11-01 12:48   ` Jens Axboe
2010-11-01 13:08     ` Mathieu Desnoyers
2010-11-01 13:34       ` Jens Axboe [this message]
2010-11-01 13:41       ` Pekka Enberg
2010-11-01 13:42         ` Jens Axboe
2010-11-01 16:00           ` Mathieu Desnoyers
2010-11-01 18:02             ` Jesper Juhl
2010-11-01 18:26               ` Mathieu Desnoyers

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=4CCEC1E6.9010806@kernel.dk \
    --to=axboe@kernel.dk \
    --cc=akpm@linux-foundation.org \
    --cc=jj@chaosbits.net \
    --cc=karim@opersys.com \
    --cc=lethal@linux-sh.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mathieu.desnoyers@polymtl.ca \
    --cc=rostedt@goodmis.org \
    --cc=zanussi@us.ibm.com \
    /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