Re: [PATCH 2/4] relayfs: Documentation for non-relay file support

[Andrew Morton]

Tom Zanussi <zanussi@xxxxxxxxxx> wrote:
>
>  +relay_open() automatically creates files in the relayfs filesystem to
>  +represent the per-cpu kernel buffers; it's often useful for
>  +applications to be able to create their own files in the relayfs
>  +filesystem as well e.g. 'control' files used to communicate control
>  +information between the kernel and user sides of a relayfs
>  +application.

What are the semantics of these control files?  How does an application
know that there's something new to be read from them?  select() or poll()
or blocking read()?

Can userspace write to the control files?   If so, what happens in-kernel?
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/