lkml.org 
[lkml]   [2005]   [Jan]   [16]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
/
Date
From
SubjectRe: 2.6.11-rc1-mm1
On Fri, Jan 14, 2005 at 04:11:38PM -0500, Karim Yaghmour wrote:
> Where does this appear in relayfs and what rights do
> user-space apps have over it (rwx).

Why would you want anything but read access?

> bufsize, nbufs:
> Usually things have to be subdivided in sub-buffers to make
> both writing and reading simple. LTT uses this to allow,
> among other things, random trace access.

I think random access is overkill. Keeping the code simple is more
important and user-space can post-process it.

> resize_min, resize_max:
> Allow for dynamic resizing of buffer.

Auto-resizing sounds like a really bad idea.

> init_buf, init_buf_size:
> Is there an initial buffer containing some data that should
> be used to initialize the channel's content. If you're doing
> init-time tracing, for example, you need to have a pre-allocated
> static buffer that is copied to relayfs once relayfs is mounted.

And why can't you do this from that code? It just needs an initcall-like
thing that runs after mounting of relayfs.

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/

\
 
 \ /
  Last update: 2005-03-22 14:09    [W:0.191 / U:0.052 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site