From: Tejun Heo <tj@kernel.org>
To: Steven Rostedt <rostedt@goodmis.org>
Cc: Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
linux-kernel@vger.kernel.org, Al Viro <viro@ZenIV.linux.org.uk>,
Ingo Molnar <mingo@kernel.org>,
Andrew Morton <akpm@linux-foundation.org>
Subject: Re: [RFC][PATCH 0/5] tracing: Add new file system tracefs
Date: Thu, 22 Jan 2015 10:24:31 -0500 [thread overview]
Message-ID: <20150122152431.GC4507@htj.dyndns.org> (raw)
In-Reply-To: <20150122101530.2175cf2b@gandalf.local.home>
On Thu, Jan 22, 2015 at 10:15:30AM -0500, Steven Rostedt wrote:
> > kernfs provides two sets of file operations. One is seq_file based
> > and the other is direct read/write. In both cases, bouncing data
> > between userland and kernel is handled by kernfs. If you already have
> > existing read write ops implemented doing custom buffer handling and
> > direct userland memory access, it'll take some adaptation but for a
> > lot of cases this would consolidate duplicate code paths.
>
> Does it also handle splice? That's a key part of the tracing code.
It doesn't yet. We can add it as a part of kernfs_syscall_ops tho
which exists to support these specialized bypass operations. kernfs
doesn't do much with these. It just passes over the calls to the
registered callbacks.
Thanks.
--
tejun
next prev parent reply other threads:[~2015-01-22 15:24 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-01-21 17:19 [RFC][PATCH 0/5] tracing: Add new file system tracefs Steven Rostedt
2015-01-21 17:19 ` [RFC][PATCH 1/5] tracefs: Add new tracefs file system Steven Rostedt
2015-01-21 18:30 ` Steven Rostedt
2015-01-21 17:19 ` [RFC][PATCH 2/5] tracing: Convert the tracing facility over to use tracefs Steven Rostedt
2015-01-21 17:32 ` Steven Rostedt
2015-01-21 17:19 ` [RFC][PATCH 3/5] tracing: Automatically mount tracefs on debugfs/tracing Steven Rostedt
2015-01-21 17:19 ` [RFC][PATCH 4/5] tracing: Have mkdir and rmdir be part of tracefs Steven Rostedt
2015-01-21 18:31 ` Steven Rostedt
2015-01-21 20:47 ` Steven Rostedt
2015-01-21 17:19 ` [RFC][PATCH 5/5] tracefs: Add directory /sys/kernel/tracing Steven Rostedt
2015-01-21 17:32 ` [RFC][PATCH 0/5] tracing: Add new file system tracefs Steven Rostedt
2015-01-21 23:00 ` Greg Kroah-Hartman
2015-01-22 1:47 ` Steven Rostedt
2015-01-22 3:07 ` Steven Rostedt
2015-01-22 3:18 ` Greg Kroah-Hartman
2015-01-22 3:51 ` Steven Rostedt
2015-01-22 12:32 ` Tejun Heo
2015-01-22 12:33 ` Tejun Heo
2015-01-22 14:32 ` Steven Rostedt
2015-01-22 14:55 ` Tejun Heo
2015-01-22 15:15 ` Steven Rostedt
2015-01-22 15:24 ` Tejun Heo [this message]
2015-01-22 4:23 ` Al Viro
2015-01-22 4:35 ` Steven Rostedt
2015-01-22 12:49 ` Tejun Heo
2015-01-22 12:26 ` Tejun Heo
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=20150122152431.GC4507@htj.dyndns.org \
--to=tj@kernel.org \
--cc=akpm@linux-foundation.org \
--cc=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@kernel.org \
--cc=rostedt@goodmis.org \
--cc=viro@ZenIV.linux.org.uk \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.