From: Mathieu Desnoyers <mathieu.desnoyers@polymtl.ca>
To: Jesper Juhl <jj@chaosbits.net>
Cc: Jens Axboe <axboe@kernel.dk>, Pekka Enberg <penberg@kernel.org>,
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, 1 Nov 2010 14:26:25 -0400 [thread overview]
Message-ID: <20101101182625.GA20005@Krystal> (raw)
In-Reply-To: <alpine.LNX.2.00.1011011900500.9616@swampdragon.chaosbits.net>
* Jesper Juhl (jj@chaosbits.net) wrote:
> On Mon, 1 Nov 2010, Mathieu Desnoyers wrote:
>
> > * Jens Axboe (axboe@kernel.dk) wrote:
> > > On 2010-11-01 09:41, Pekka Enberg 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.
> > > >
> > > > On Mon, Nov 1, 2010 at 3:08 PM, Mathieu Desnoyers
> > > > <mathieu.desnoyers@polymtl.ca> wrote:
> > > >> 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.
> > > >
> > > > We don't in general NAK cleanups because of future features or
> > > > removals that may or may not happen.
> > >
> > > Agree, this is parallel to whether or not we can transition blktrace to
> > > using the generic ring buffer library or not. If the current patch
> > > proposed makes sense, then it should go in regardless of
> > > potential/future plans.
> >
> > Agreed. Thanks,
> >
>
> As I read the discussion over the last day or so, since I last checked my
> mail, there are no longer any objections to the patch. Correct?
Yes,
Acked-by: Mathieu Desnoyers <mathieu.desnoyers@efficios.com>
> If that's the case, who will merge it? and should I resend it with various
> peoples Acked-by: lines? or?
Yep, this might make the maintainer's work easier, I think. As for who
will merge it, good question. Andrew ?
Thanks,
Mathieu
--
Mathieu Desnoyers
Operating System Efficiency R&D Consultant
EfficiOS Inc.
http://www.efficios.com
prev parent reply other threads:[~2010-11-01 18:36 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
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 [this message]
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=20101101182625.GA20005@Krystal \
--to=mathieu.desnoyers@polymtl.ca \
--cc=akpm@linux-foundation.org \
--cc=axboe@kernel.dk \
--cc=jj@chaosbits.net \
--cc=karim@opersys.com \
--cc=lethal@linux-sh.org \
--cc=linux-kernel@vger.kernel.org \
--cc=penberg@kernel.org \
--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