From: Ingo Molnar <mingo@elte.hu>
To: Eduard - Gabriel Munteanu <eduard.munteanu@linux360.ro>
Cc: fweisbec@gmail.com, penberg@cs.helsinki.fi, rostedt@goodmis.org,
linux-kernel@vger.kernel.org
Subject: Re: [RFC PATCH 2/2] trace: splice support for tracing_pipe
Date: Mon, 9 Feb 2009 10:04:33 +0100 [thread overview]
Message-ID: <20090209090433.GB31890@elte.hu> (raw)
In-Reply-To: <da7111334b2e95966758bf982a7bcf3b31ccba9c.1234159200.git.eduard.munteanu@linux360.ro>
* Eduard - Gabriel Munteanu <eduard.munteanu@linux360.ro> wrote:
> Added and implemented tracing_pipe_fops->splice_read(). This allows
> userspace programs to get tracing data more efficiently.
Cool!
The structure of the splice state machine looks good - havent tested it yet.
A few comments:
> +static struct pipe_buf_operations tracing_pipe_buf_ops = {
> + .can_merge = 0,
> + .map = generic_pipe_buf_map,
> + .unmap = generic_pipe_buf_unmap,
> + .confirm = generic_pipe_buf_confirm,
> + .release = tracing_pipe_buf_release,
> + .steal = generic_pipe_buf_steal,
> + .get = generic_pipe_buf_get,
> +};
this looks nicer:
static struct pipe_buf_operations tracing_pipe_buf_ops = {
.can_merge = 0,
.map = generic_pipe_buf_map,
.unmap = generic_pipe_buf_unmap,
.confirm = generic_pipe_buf_confirm,
.release = tracing_pipe_buf_release,
.steal = generic_pipe_buf_steal,
.get = generic_pipe_buf_get,
};
(and this is how we do these things elsewhere in the tracing code)
ditto:
> + struct splice_pipe_desc spd = {
> + .pages = pages,
> + .partial = partial,
> + .nr_pages = 0, /* This gets updated below. */
> + .flags = flags,
> + .ops = &tracing_pipe_buf_ops,
> + .spd_release = tracing_spd_release_pipe,
> + };
+ for (i = 0, rem = len; i < PIPE_BUFFERS && rem; i++) {
+ pages[i] = alloc_page(GFP_KERNEL);
+
+ /* Seq buffer is page-sized, exactly what we need. */
+ for (;;) {
Ok, that's a minor bug: should check for NULL alloc_page() return.
> +out:
> + mutex_unlock(&trace_types_lock);
> +
> + return ret;
please name this label as 'out_err' - which it really is. We generally use the
'out:' label for error-less exits.
Btw., this is how we do structure initializations:
> .open = tracing_open_pipe,
> .poll = tracing_poll_pipe,
> .read = tracing_read_pipe,
> + .splice_read = tracing_splice_read_pipe,
> .release = tracing_release_pipe,
> };
One more thing, i'd suggest to split this loop (which is an iterator in a larger
loop):
+ /* Seq buffer is page-sized, exactly what we need. */
+ for (;;) {
+ count = iter->seq.len;
+ ret = print_trace_line(iter);
[...]
+ }
Out into a separate helper inline function. This really is a "fill in pipe page"
logic and having it separate makes it easier to review the splice-loop code pattern
itself.
Thanks,
Ingo
next prev parent reply other threads:[~2009-02-09 9:05 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-02-09 6:15 [RFC PATCH 0/2] splice patches for ftrace Eduard - Gabriel Munteanu
2009-02-09 6:15 ` [RFC PATCH 1/2] trace: Move pipe waiting code out of tracing_read_pipe() Eduard - Gabriel Munteanu
2009-02-09 6:15 ` [RFC PATCH 2/2] trace: splice support for tracing_pipe Eduard - Gabriel Munteanu
2009-02-09 9:04 ` Ingo Molnar [this message]
2009-02-09 15:49 ` Steven Rostedt
2009-02-11 12:35 ` Ingo Molnar
2009-02-11 13:19 ` Frederic Weisbecker
2009-02-09 14:10 ` [RFC PATCH 0/2] splice patches for ftrace Steven Rostedt
2009-02-09 14:17 ` Ingo Molnar
2009-02-09 14:43 ` Pekka Enberg
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=20090209090433.GB31890@elte.hu \
--to=mingo@elte.hu \
--cc=eduard.munteanu@linux360.ro \
--cc=fweisbec@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=penberg@cs.helsinki.fi \
--cc=rostedt@goodmis.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
all inboxes | Powered by JetHome®