[PATCH] relayfs
Here's the latest version of relayfs, against linux-2.6.11-mm2. I'm hoping
you'll consider putting this version back into your tree - the previous
rounds of comment seem to have shaken out all the API issues and the number
of comments on the code itself have also steadily dwindled.
This patch is essentially the same as the relayfs redux part 5 patch, with
some minor changes based on reviewer comments. Thanks again to Pekka
Enberg for those. The patch size without documentation is now a little
smaller at just over 40k. Here's a detailed list of the changes:
- removed the attribute_flags in relay open and changed it to a
boolean specifying either overwrite or no-overwrite mode, and removed
everything referencing the attribute flags.
- added a check for NULL names in relayfs_create_entry()
- got rid of the unnecessary multiple labels in relay_create_buf()
- some minor simplification of relay_alloc_buf() which got rid of a
couple params
- updated the Documentation
In addition, this version (through code contained in the relay-apps tarball
linked to below, not as part of the relayfs patch) tries to make it as easy
as possible to create the cooperating kernel/user pieces of a typical and
common type of logging application, one where kernel logging is kicked off
when a user space data collection app starts and stops when the collection
app exits, with the data being automatically logged to disk in between. To
create this type of application, you basically just include a header file
(relay-app.h, included in the relay-apps tarball) in your kernel module,
define a couple of callbacks and call an initialization function, and on
the user side call a single function that sets up and continuously monitors
the buffers, and writes data to files as it becomes available. Channels
are created when the collection app is started and destroyed when it exits,
not when the kernel module is inserted, so different channel buffer sizes
can be specified for each separate run via command-line options. See the
README in the relay-apps tarball for details.
Also included in the relay-apps tarball are a couple examples
demonstrating how you can use this to create quick and dirty kernel
logging/debugging applications. They are:
- tprintk, short for 'tee printk', which temporarily puts a kprobe on
printk() and writes a duplicate stream of printk output to a relayfs
channel. This could be used anywhere there's printk() debugging code
in the kernel which you'd like to exercise, but would rather not have
your system logs cluttered with debugging junk. You'd probably want
to kill klogd while you do this, otherwise there wouldn't be much
point (since putting a kprobe on printk() doesn't change the output
of printk()). I've used this method to temporarily divert the packet
logging output of the iptables LOG target from the system logs to
relayfs files instead, for instance.
- klog, which just provides a printk-like formatted logging function
on top of relayfs. Again, you can use this to keep stuff out of your
system logs if used in place of printk.
The example applications can be found here:
http://prdownloads.sourceforge.net/dprobes/relay-apps.tar.gz?download
From: Christoph Hellwig <hch@lst.de>
avoid lookup_hash usage in relayfs
Signed-off-by: Tom Zanussi <zanussi@us.ibm.com>
Signed-off-by: Andrew Morton <akpm@osdl.org>
Signed-off-by: Linus Torvalds <torvalds@osdl.org>
2005-09-07 00:16:30 +02:00
|
|
|
/*
|
|
|
|
* linux/include/linux/relayfs_fs.h
|
|
|
|
*
|
|
|
|
* Copyright (C) 2002, 2003 - Tom Zanussi (zanussi@us.ibm.com), IBM Corp
|
|
|
|
* Copyright (C) 1999, 2000, 2001, 2002 - Karim Yaghmour (karim@opersys.com)
|
|
|
|
*
|
|
|
|
* RelayFS definitions and declarations
|
|
|
|
*/
|
|
|
|
|
|
|
|
#ifndef _LINUX_RELAYFS_FS_H
|
|
|
|
#define _LINUX_RELAYFS_FS_H
|
|
|
|
|
|
|
|
#include <linux/config.h>
|
|
|
|
#include <linux/types.h>
|
|
|
|
#include <linux/sched.h>
|
|
|
|
#include <linux/wait.h>
|
|
|
|
#include <linux/list.h>
|
|
|
|
#include <linux/fs.h>
|
|
|
|
#include <linux/poll.h>
|
|
|
|
#include <linux/kref.h>
|
|
|
|
|
|
|
|
/*
|
2005-12-20 20:10:22 +01:00
|
|
|
* Tracks changes to rchan/rchan_buf structs
|
[PATCH] relayfs
Here's the latest version of relayfs, against linux-2.6.11-mm2. I'm hoping
you'll consider putting this version back into your tree - the previous
rounds of comment seem to have shaken out all the API issues and the number
of comments on the code itself have also steadily dwindled.
This patch is essentially the same as the relayfs redux part 5 patch, with
some minor changes based on reviewer comments. Thanks again to Pekka
Enberg for those. The patch size without documentation is now a little
smaller at just over 40k. Here's a detailed list of the changes:
- removed the attribute_flags in relay open and changed it to a
boolean specifying either overwrite or no-overwrite mode, and removed
everything referencing the attribute flags.
- added a check for NULL names in relayfs_create_entry()
- got rid of the unnecessary multiple labels in relay_create_buf()
- some minor simplification of relay_alloc_buf() which got rid of a
couple params
- updated the Documentation
In addition, this version (through code contained in the relay-apps tarball
linked to below, not as part of the relayfs patch) tries to make it as easy
as possible to create the cooperating kernel/user pieces of a typical and
common type of logging application, one where kernel logging is kicked off
when a user space data collection app starts and stops when the collection
app exits, with the data being automatically logged to disk in between. To
create this type of application, you basically just include a header file
(relay-app.h, included in the relay-apps tarball) in your kernel module,
define a couple of callbacks and call an initialization function, and on
the user side call a single function that sets up and continuously monitors
the buffers, and writes data to files as it becomes available. Channels
are created when the collection app is started and destroyed when it exits,
not when the kernel module is inserted, so different channel buffer sizes
can be specified for each separate run via command-line options. See the
README in the relay-apps tarball for details.
Also included in the relay-apps tarball are a couple examples
demonstrating how you can use this to create quick and dirty kernel
logging/debugging applications. They are:
- tprintk, short for 'tee printk', which temporarily puts a kprobe on
printk() and writes a duplicate stream of printk output to a relayfs
channel. This could be used anywhere there's printk() debugging code
in the kernel which you'd like to exercise, but would rather not have
your system logs cluttered with debugging junk. You'd probably want
to kill klogd while you do this, otherwise there wouldn't be much
point (since putting a kprobe on printk() doesn't change the output
of printk()). I've used this method to temporarily divert the packet
logging output of the iptables LOG target from the system logs to
relayfs files instead, for instance.
- klog, which just provides a printk-like formatted logging function
on top of relayfs. Again, you can use this to keep stuff out of your
system logs if used in place of printk.
The example applications can be found here:
http://prdownloads.sourceforge.net/dprobes/relay-apps.tar.gz?download
From: Christoph Hellwig <hch@lst.de>
avoid lookup_hash usage in relayfs
Signed-off-by: Tom Zanussi <zanussi@us.ibm.com>
Signed-off-by: Andrew Morton <akpm@osdl.org>
Signed-off-by: Linus Torvalds <torvalds@osdl.org>
2005-09-07 00:16:30 +02:00
|
|
|
*/
|
2005-12-20 20:10:22 +01:00
|
|
|
#define RELAYFS_CHANNEL_VERSION 6
|
[PATCH] relayfs
Here's the latest version of relayfs, against linux-2.6.11-mm2. I'm hoping
you'll consider putting this version back into your tree - the previous
rounds of comment seem to have shaken out all the API issues and the number
of comments on the code itself have also steadily dwindled.
This patch is essentially the same as the relayfs redux part 5 patch, with
some minor changes based on reviewer comments. Thanks again to Pekka
Enberg for those. The patch size without documentation is now a little
smaller at just over 40k. Here's a detailed list of the changes:
- removed the attribute_flags in relay open and changed it to a
boolean specifying either overwrite or no-overwrite mode, and removed
everything referencing the attribute flags.
- added a check for NULL names in relayfs_create_entry()
- got rid of the unnecessary multiple labels in relay_create_buf()
- some minor simplification of relay_alloc_buf() which got rid of a
couple params
- updated the Documentation
In addition, this version (through code contained in the relay-apps tarball
linked to below, not as part of the relayfs patch) tries to make it as easy
as possible to create the cooperating kernel/user pieces of a typical and
common type of logging application, one where kernel logging is kicked off
when a user space data collection app starts and stops when the collection
app exits, with the data being automatically logged to disk in between. To
create this type of application, you basically just include a header file
(relay-app.h, included in the relay-apps tarball) in your kernel module,
define a couple of callbacks and call an initialization function, and on
the user side call a single function that sets up and continuously monitors
the buffers, and writes data to files as it becomes available. Channels
are created when the collection app is started and destroyed when it exits,
not when the kernel module is inserted, so different channel buffer sizes
can be specified for each separate run via command-line options. See the
README in the relay-apps tarball for details.
Also included in the relay-apps tarball are a couple examples
demonstrating how you can use this to create quick and dirty kernel
logging/debugging applications. They are:
- tprintk, short for 'tee printk', which temporarily puts a kprobe on
printk() and writes a duplicate stream of printk output to a relayfs
channel. This could be used anywhere there's printk() debugging code
in the kernel which you'd like to exercise, but would rather not have
your system logs cluttered with debugging junk. You'd probably want
to kill klogd while you do this, otherwise there wouldn't be much
point (since putting a kprobe on printk() doesn't change the output
of printk()). I've used this method to temporarily divert the packet
logging output of the iptables LOG target from the system logs to
relayfs files instead, for instance.
- klog, which just provides a printk-like formatted logging function
on top of relayfs. Again, you can use this to keep stuff out of your
system logs if used in place of printk.
The example applications can be found here:
http://prdownloads.sourceforge.net/dprobes/relay-apps.tar.gz?download
From: Christoph Hellwig <hch@lst.de>
avoid lookup_hash usage in relayfs
Signed-off-by: Tom Zanussi <zanussi@us.ibm.com>
Signed-off-by: Andrew Morton <akpm@osdl.org>
Signed-off-by: Linus Torvalds <torvalds@osdl.org>
2005-09-07 00:16:30 +02:00
|
|
|
|
|
|
|
/*
|
|
|
|
* Per-cpu relay channel buffer
|
|
|
|
*/
|
|
|
|
struct rchan_buf
|
|
|
|
{
|
|
|
|
void *start; /* start of channel buffer */
|
|
|
|
void *data; /* start of current sub-buffer */
|
|
|
|
size_t offset; /* current offset into sub-buffer */
|
|
|
|
size_t subbufs_produced; /* count of sub-buffers produced */
|
|
|
|
size_t subbufs_consumed; /* count of sub-buffers consumed */
|
|
|
|
struct rchan *chan; /* associated channel */
|
|
|
|
wait_queue_head_t read_wait; /* reader wait queue */
|
|
|
|
struct work_struct wake_readers; /* reader wake-up work struct */
|
|
|
|
struct dentry *dentry; /* channel file dentry */
|
|
|
|
struct kref kref; /* channel buffer refcount */
|
|
|
|
struct page **page_array; /* array of current buffer pages */
|
|
|
|
unsigned int page_count; /* number of current buffer pages */
|
|
|
|
unsigned int finalized; /* buffer has been finalized */
|
|
|
|
size_t *padding; /* padding counts per sub-buffer */
|
|
|
|
size_t prev_padding; /* temporary variable */
|
|
|
|
size_t bytes_consumed; /* bytes consumed in cur read subbuf */
|
|
|
|
unsigned int cpu; /* this buf's cpu */
|
|
|
|
} ____cacheline_aligned;
|
|
|
|
|
|
|
|
/*
|
|
|
|
* Relay channel data structure
|
|
|
|
*/
|
|
|
|
struct rchan
|
|
|
|
{
|
|
|
|
u32 version; /* the version of this struct */
|
|
|
|
size_t subbuf_size; /* sub-buffer size */
|
|
|
|
size_t n_subbufs; /* number of sub-buffers per buffer */
|
|
|
|
size_t alloc_size; /* total buffer size allocated */
|
|
|
|
struct rchan_callbacks *cb; /* client callbacks */
|
|
|
|
struct kref kref; /* channel refcount */
|
|
|
|
void *private_data; /* for user-defined data */
|
2005-12-20 20:10:22 +01:00
|
|
|
size_t last_toobig; /* tried to log event > subbuf size */
|
[PATCH] relayfs
Here's the latest version of relayfs, against linux-2.6.11-mm2. I'm hoping
you'll consider putting this version back into your tree - the previous
rounds of comment seem to have shaken out all the API issues and the number
of comments on the code itself have also steadily dwindled.
This patch is essentially the same as the relayfs redux part 5 patch, with
some minor changes based on reviewer comments. Thanks again to Pekka
Enberg for those. The patch size without documentation is now a little
smaller at just over 40k. Here's a detailed list of the changes:
- removed the attribute_flags in relay open and changed it to a
boolean specifying either overwrite or no-overwrite mode, and removed
everything referencing the attribute flags.
- added a check for NULL names in relayfs_create_entry()
- got rid of the unnecessary multiple labels in relay_create_buf()
- some minor simplification of relay_alloc_buf() which got rid of a
couple params
- updated the Documentation
In addition, this version (through code contained in the relay-apps tarball
linked to below, not as part of the relayfs patch) tries to make it as easy
as possible to create the cooperating kernel/user pieces of a typical and
common type of logging application, one where kernel logging is kicked off
when a user space data collection app starts and stops when the collection
app exits, with the data being automatically logged to disk in between. To
create this type of application, you basically just include a header file
(relay-app.h, included in the relay-apps tarball) in your kernel module,
define a couple of callbacks and call an initialization function, and on
the user side call a single function that sets up and continuously monitors
the buffers, and writes data to files as it becomes available. Channels
are created when the collection app is started and destroyed when it exits,
not when the kernel module is inserted, so different channel buffer sizes
can be specified for each separate run via command-line options. See the
README in the relay-apps tarball for details.
Also included in the relay-apps tarball are a couple examples
demonstrating how you can use this to create quick and dirty kernel
logging/debugging applications. They are:
- tprintk, short for 'tee printk', which temporarily puts a kprobe on
printk() and writes a duplicate stream of printk output to a relayfs
channel. This could be used anywhere there's printk() debugging code
in the kernel which you'd like to exercise, but would rather not have
your system logs cluttered with debugging junk. You'd probably want
to kill klogd while you do this, otherwise there wouldn't be much
point (since putting a kprobe on printk() doesn't change the output
of printk()). I've used this method to temporarily divert the packet
logging output of the iptables LOG target from the system logs to
relayfs files instead, for instance.
- klog, which just provides a printk-like formatted logging function
on top of relayfs. Again, you can use this to keep stuff out of your
system logs if used in place of printk.
The example applications can be found here:
http://prdownloads.sourceforge.net/dprobes/relay-apps.tar.gz?download
From: Christoph Hellwig <hch@lst.de>
avoid lookup_hash usage in relayfs
Signed-off-by: Tom Zanussi <zanussi@us.ibm.com>
Signed-off-by: Andrew Morton <akpm@osdl.org>
Signed-off-by: Linus Torvalds <torvalds@osdl.org>
2005-09-07 00:16:30 +02:00
|
|
|
struct rchan_buf *buf[NR_CPUS]; /* per-cpu channel buffers */
|
|
|
|
};
|
|
|
|
|
|
|
|
/*
|
|
|
|
* Relay channel client callbacks
|
|
|
|
*/
|
|
|
|
struct rchan_callbacks
|
|
|
|
{
|
|
|
|
/*
|
|
|
|
* subbuf_start - called on buffer-switch to a new sub-buffer
|
|
|
|
* @buf: the channel buffer containing the new sub-buffer
|
|
|
|
* @subbuf: the start of the new sub-buffer
|
|
|
|
* @prev_subbuf: the start of the previous sub-buffer
|
|
|
|
* @prev_padding: unused space at the end of previous sub-buffer
|
|
|
|
*
|
|
|
|
* The client should return 1 to continue logging, 0 to stop
|
|
|
|
* logging.
|
|
|
|
*
|
|
|
|
* NOTE: subbuf_start will also be invoked when the buffer is
|
|
|
|
* created, so that the first sub-buffer can be initialized
|
|
|
|
* if necessary. In this case, prev_subbuf will be NULL.
|
|
|
|
*
|
|
|
|
* NOTE: the client can reserve bytes at the beginning of the new
|
|
|
|
* sub-buffer by calling subbuf_start_reserve() in this callback.
|
|
|
|
*/
|
|
|
|
int (*subbuf_start) (struct rchan_buf *buf,
|
|
|
|
void *subbuf,
|
|
|
|
void *prev_subbuf,
|
|
|
|
size_t prev_padding);
|
|
|
|
|
|
|
|
/*
|
|
|
|
* buf_mapped - relayfs buffer mmap notification
|
|
|
|
* @buf: the channel buffer
|
|
|
|
* @filp: relayfs file pointer
|
|
|
|
*
|
|
|
|
* Called when a relayfs file is successfully mmapped
|
|
|
|
*/
|
|
|
|
void (*buf_mapped)(struct rchan_buf *buf,
|
|
|
|
struct file *filp);
|
|
|
|
|
|
|
|
/*
|
|
|
|
* buf_unmapped - relayfs buffer unmap notification
|
|
|
|
* @buf: the channel buffer
|
|
|
|
* @filp: relayfs file pointer
|
|
|
|
*
|
|
|
|
* Called when a relayfs file is successfully unmapped
|
|
|
|
*/
|
|
|
|
void (*buf_unmapped)(struct rchan_buf *buf,
|
|
|
|
struct file *filp);
|
2006-01-08 10:02:28 +01:00
|
|
|
/*
|
|
|
|
* create_buf_file - create file to represent a relayfs channel buffer
|
|
|
|
* @filename: the name of the file to create
|
|
|
|
* @parent: the parent of the file to create
|
|
|
|
* @mode: the mode of the file to create
|
|
|
|
* @buf: the channel buffer
|
2006-01-08 10:02:29 +01:00
|
|
|
* @is_global: outparam - set non-zero if the buffer should be global
|
2006-01-08 10:02:28 +01:00
|
|
|
*
|
|
|
|
* Called during relay_open(), once for each per-cpu buffer,
|
|
|
|
* to allow the client to create a file to be used to
|
|
|
|
* represent the corresponding channel buffer. If the file is
|
|
|
|
* created outside of relayfs, the parent must also exist in
|
|
|
|
* that filesystem.
|
|
|
|
*
|
|
|
|
* The callback should return the dentry of the file created
|
|
|
|
* to represent the relay buffer.
|
|
|
|
*
|
2006-01-08 10:02:29 +01:00
|
|
|
* Setting the is_global outparam to a non-zero value will
|
|
|
|
* cause relay_open() to create a single global buffer rather
|
|
|
|
* than the default set of per-cpu buffers.
|
|
|
|
*
|
2006-01-08 10:02:28 +01:00
|
|
|
* See Documentation/filesystems/relayfs.txt for more info.
|
|
|
|
*/
|
|
|
|
struct dentry *(*create_buf_file)(const char *filename,
|
|
|
|
struct dentry *parent,
|
|
|
|
int mode,
|
2006-01-08 10:02:29 +01:00
|
|
|
struct rchan_buf *buf,
|
|
|
|
int *is_global);
|
2006-01-08 10:02:28 +01:00
|
|
|
|
|
|
|
/*
|
|
|
|
* remove_buf_file - remove file representing a relayfs channel buffer
|
|
|
|
* @dentry: the dentry of the file to remove
|
|
|
|
*
|
|
|
|
* Called during relay_close(), once for each per-cpu buffer,
|
|
|
|
* to allow the client to remove a file used to represent a
|
|
|
|
* channel buffer.
|
|
|
|
*
|
|
|
|
* The callback should return 0 if successful, negative if not.
|
|
|
|
*/
|
|
|
|
int (*remove_buf_file)(struct dentry *dentry);
|
[PATCH] relayfs
Here's the latest version of relayfs, against linux-2.6.11-mm2. I'm hoping
you'll consider putting this version back into your tree - the previous
rounds of comment seem to have shaken out all the API issues and the number
of comments on the code itself have also steadily dwindled.
This patch is essentially the same as the relayfs redux part 5 patch, with
some minor changes based on reviewer comments. Thanks again to Pekka
Enberg for those. The patch size without documentation is now a little
smaller at just over 40k. Here's a detailed list of the changes:
- removed the attribute_flags in relay open and changed it to a
boolean specifying either overwrite or no-overwrite mode, and removed
everything referencing the attribute flags.
- added a check for NULL names in relayfs_create_entry()
- got rid of the unnecessary multiple labels in relay_create_buf()
- some minor simplification of relay_alloc_buf() which got rid of a
couple params
- updated the Documentation
In addition, this version (through code contained in the relay-apps tarball
linked to below, not as part of the relayfs patch) tries to make it as easy
as possible to create the cooperating kernel/user pieces of a typical and
common type of logging application, one where kernel logging is kicked off
when a user space data collection app starts and stops when the collection
app exits, with the data being automatically logged to disk in between. To
create this type of application, you basically just include a header file
(relay-app.h, included in the relay-apps tarball) in your kernel module,
define a couple of callbacks and call an initialization function, and on
the user side call a single function that sets up and continuously monitors
the buffers, and writes data to files as it becomes available. Channels
are created when the collection app is started and destroyed when it exits,
not when the kernel module is inserted, so different channel buffer sizes
can be specified for each separate run via command-line options. See the
README in the relay-apps tarball for details.
Also included in the relay-apps tarball are a couple examples
demonstrating how you can use this to create quick and dirty kernel
logging/debugging applications. They are:
- tprintk, short for 'tee printk', which temporarily puts a kprobe on
printk() and writes a duplicate stream of printk output to a relayfs
channel. This could be used anywhere there's printk() debugging code
in the kernel which you'd like to exercise, but would rather not have
your system logs cluttered with debugging junk. You'd probably want
to kill klogd while you do this, otherwise there wouldn't be much
point (since putting a kprobe on printk() doesn't change the output
of printk()). I've used this method to temporarily divert the packet
logging output of the iptables LOG target from the system logs to
relayfs files instead, for instance.
- klog, which just provides a printk-like formatted logging function
on top of relayfs. Again, you can use this to keep stuff out of your
system logs if used in place of printk.
The example applications can be found here:
http://prdownloads.sourceforge.net/dprobes/relay-apps.tar.gz?download
From: Christoph Hellwig <hch@lst.de>
avoid lookup_hash usage in relayfs
Signed-off-by: Tom Zanussi <zanussi@us.ibm.com>
Signed-off-by: Andrew Morton <akpm@osdl.org>
Signed-off-by: Linus Torvalds <torvalds@osdl.org>
2005-09-07 00:16:30 +02:00
|
|
|
};
|
|
|
|
|
|
|
|
/*
|
|
|
|
* relayfs kernel API, fs/relayfs/relay.c
|
|
|
|
*/
|
|
|
|
|
|
|
|
struct rchan *relay_open(const char *base_filename,
|
|
|
|
struct dentry *parent,
|
|
|
|
size_t subbuf_size,
|
|
|
|
size_t n_subbufs,
|
|
|
|
struct rchan_callbacks *cb);
|
|
|
|
extern void relay_close(struct rchan *chan);
|
|
|
|
extern void relay_flush(struct rchan *chan);
|
|
|
|
extern void relay_subbufs_consumed(struct rchan *chan,
|
|
|
|
unsigned int cpu,
|
|
|
|
size_t consumed);
|
|
|
|
extern void relay_reset(struct rchan *chan);
|
|
|
|
extern int relay_buf_full(struct rchan_buf *buf);
|
|
|
|
|
|
|
|
extern size_t relay_switch_subbuf(struct rchan_buf *buf,
|
|
|
|
size_t length);
|
|
|
|
extern struct dentry *relayfs_create_dir(const char *name,
|
|
|
|
struct dentry *parent);
|
|
|
|
extern int relayfs_remove_dir(struct dentry *dentry);
|
2006-01-08 10:02:24 +01:00
|
|
|
extern struct dentry *relayfs_create_file(const char *name,
|
|
|
|
struct dentry *parent,
|
|
|
|
int mode,
|
|
|
|
struct file_operations *fops,
|
|
|
|
void *data);
|
2006-01-08 10:02:25 +01:00
|
|
|
extern int relayfs_remove_file(struct dentry *dentry);
|
[PATCH] relayfs
Here's the latest version of relayfs, against linux-2.6.11-mm2. I'm hoping
you'll consider putting this version back into your tree - the previous
rounds of comment seem to have shaken out all the API issues and the number
of comments on the code itself have also steadily dwindled.
This patch is essentially the same as the relayfs redux part 5 patch, with
some minor changes based on reviewer comments. Thanks again to Pekka
Enberg for those. The patch size without documentation is now a little
smaller at just over 40k. Here's a detailed list of the changes:
- removed the attribute_flags in relay open and changed it to a
boolean specifying either overwrite or no-overwrite mode, and removed
everything referencing the attribute flags.
- added a check for NULL names in relayfs_create_entry()
- got rid of the unnecessary multiple labels in relay_create_buf()
- some minor simplification of relay_alloc_buf() which got rid of a
couple params
- updated the Documentation
In addition, this version (through code contained in the relay-apps tarball
linked to below, not as part of the relayfs patch) tries to make it as easy
as possible to create the cooperating kernel/user pieces of a typical and
common type of logging application, one where kernel logging is kicked off
when a user space data collection app starts and stops when the collection
app exits, with the data being automatically logged to disk in between. To
create this type of application, you basically just include a header file
(relay-app.h, included in the relay-apps tarball) in your kernel module,
define a couple of callbacks and call an initialization function, and on
the user side call a single function that sets up and continuously monitors
the buffers, and writes data to files as it becomes available. Channels
are created when the collection app is started and destroyed when it exits,
not when the kernel module is inserted, so different channel buffer sizes
can be specified for each separate run via command-line options. See the
README in the relay-apps tarball for details.
Also included in the relay-apps tarball are a couple examples
demonstrating how you can use this to create quick and dirty kernel
logging/debugging applications. They are:
- tprintk, short for 'tee printk', which temporarily puts a kprobe on
printk() and writes a duplicate stream of printk output to a relayfs
channel. This could be used anywhere there's printk() debugging code
in the kernel which you'd like to exercise, but would rather not have
your system logs cluttered with debugging junk. You'd probably want
to kill klogd while you do this, otherwise there wouldn't be much
point (since putting a kprobe on printk() doesn't change the output
of printk()). I've used this method to temporarily divert the packet
logging output of the iptables LOG target from the system logs to
relayfs files instead, for instance.
- klog, which just provides a printk-like formatted logging function
on top of relayfs. Again, you can use this to keep stuff out of your
system logs if used in place of printk.
The example applications can be found here:
http://prdownloads.sourceforge.net/dprobes/relay-apps.tar.gz?download
From: Christoph Hellwig <hch@lst.de>
avoid lookup_hash usage in relayfs
Signed-off-by: Tom Zanussi <zanussi@us.ibm.com>
Signed-off-by: Andrew Morton <akpm@osdl.org>
Signed-off-by: Linus Torvalds <torvalds@osdl.org>
2005-09-07 00:16:30 +02:00
|
|
|
|
|
|
|
/**
|
|
|
|
* relay_write - write data into the channel
|
|
|
|
* @chan: relay channel
|
|
|
|
* @data: data to be written
|
|
|
|
* @length: number of bytes to write
|
|
|
|
*
|
|
|
|
* Writes data into the current cpu's channel buffer.
|
|
|
|
*
|
|
|
|
* Protects the buffer by disabling interrupts. Use this
|
|
|
|
* if you might be logging from interrupt context. Try
|
|
|
|
* __relay_write() if you know you won't be logging from
|
|
|
|
* interrupt context.
|
|
|
|
*/
|
|
|
|
static inline void relay_write(struct rchan *chan,
|
|
|
|
const void *data,
|
|
|
|
size_t length)
|
|
|
|
{
|
|
|
|
unsigned long flags;
|
|
|
|
struct rchan_buf *buf;
|
|
|
|
|
|
|
|
local_irq_save(flags);
|
|
|
|
buf = chan->buf[smp_processor_id()];
|
|
|
|
if (unlikely(buf->offset + length > chan->subbuf_size))
|
|
|
|
length = relay_switch_subbuf(buf, length);
|
|
|
|
memcpy(buf->data + buf->offset, data, length);
|
|
|
|
buf->offset += length;
|
|
|
|
local_irq_restore(flags);
|
|
|
|
}
|
|
|
|
|
|
|
|
/**
|
|
|
|
* __relay_write - write data into the channel
|
|
|
|
* @chan: relay channel
|
|
|
|
* @data: data to be written
|
|
|
|
* @length: number of bytes to write
|
|
|
|
*
|
|
|
|
* Writes data into the current cpu's channel buffer.
|
|
|
|
*
|
|
|
|
* Protects the buffer by disabling preemption. Use
|
|
|
|
* relay_write() if you might be logging from interrupt
|
|
|
|
* context.
|
|
|
|
*/
|
|
|
|
static inline void __relay_write(struct rchan *chan,
|
|
|
|
const void *data,
|
|
|
|
size_t length)
|
|
|
|
{
|
|
|
|
struct rchan_buf *buf;
|
|
|
|
|
|
|
|
buf = chan->buf[get_cpu()];
|
|
|
|
if (unlikely(buf->offset + length > buf->chan->subbuf_size))
|
|
|
|
length = relay_switch_subbuf(buf, length);
|
|
|
|
memcpy(buf->data + buf->offset, data, length);
|
|
|
|
buf->offset += length;
|
|
|
|
put_cpu();
|
|
|
|
}
|
|
|
|
|
|
|
|
/**
|
|
|
|
* relay_reserve - reserve slot in channel buffer
|
|
|
|
* @chan: relay channel
|
|
|
|
* @length: number of bytes to reserve
|
|
|
|
*
|
|
|
|
* Returns pointer to reserved slot, NULL if full.
|
|
|
|
*
|
|
|
|
* Reserves a slot in the current cpu's channel buffer.
|
|
|
|
* Does not protect the buffer at all - caller must provide
|
|
|
|
* appropriate synchronization.
|
|
|
|
*/
|
|
|
|
static inline void *relay_reserve(struct rchan *chan, size_t length)
|
|
|
|
{
|
|
|
|
void *reserved;
|
|
|
|
struct rchan_buf *buf = chan->buf[smp_processor_id()];
|
|
|
|
|
|
|
|
if (unlikely(buf->offset + length > buf->chan->subbuf_size)) {
|
|
|
|
length = relay_switch_subbuf(buf, length);
|
|
|
|
if (!length)
|
|
|
|
return NULL;
|
|
|
|
}
|
|
|
|
reserved = buf->data + buf->offset;
|
|
|
|
buf->offset += length;
|
|
|
|
|
|
|
|
return reserved;
|
|
|
|
}
|
|
|
|
|
|
|
|
/**
|
|
|
|
* subbuf_start_reserve - reserve bytes at the start of a sub-buffer
|
|
|
|
* @buf: relay channel buffer
|
|
|
|
* @length: number of bytes to reserve
|
|
|
|
*
|
|
|
|
* Helper function used to reserve bytes at the beginning of
|
|
|
|
* a sub-buffer in the subbuf_start() callback.
|
|
|
|
*/
|
|
|
|
static inline void subbuf_start_reserve(struct rchan_buf *buf,
|
|
|
|
size_t length)
|
|
|
|
{
|
|
|
|
BUG_ON(length >= buf->chan->subbuf_size - 1);
|
|
|
|
buf->offset = length;
|
|
|
|
}
|
|
|
|
|
|
|
|
/*
|
2006-01-08 10:02:31 +01:00
|
|
|
* exported relay file operations, fs/relayfs/inode.c
|
[PATCH] relayfs
Here's the latest version of relayfs, against linux-2.6.11-mm2. I'm hoping
you'll consider putting this version back into your tree - the previous
rounds of comment seem to have shaken out all the API issues and the number
of comments on the code itself have also steadily dwindled.
This patch is essentially the same as the relayfs redux part 5 patch, with
some minor changes based on reviewer comments. Thanks again to Pekka
Enberg for those. The patch size without documentation is now a little
smaller at just over 40k. Here's a detailed list of the changes:
- removed the attribute_flags in relay open and changed it to a
boolean specifying either overwrite or no-overwrite mode, and removed
everything referencing the attribute flags.
- added a check for NULL names in relayfs_create_entry()
- got rid of the unnecessary multiple labels in relay_create_buf()
- some minor simplification of relay_alloc_buf() which got rid of a
couple params
- updated the Documentation
In addition, this version (through code contained in the relay-apps tarball
linked to below, not as part of the relayfs patch) tries to make it as easy
as possible to create the cooperating kernel/user pieces of a typical and
common type of logging application, one where kernel logging is kicked off
when a user space data collection app starts and stops when the collection
app exits, with the data being automatically logged to disk in between. To
create this type of application, you basically just include a header file
(relay-app.h, included in the relay-apps tarball) in your kernel module,
define a couple of callbacks and call an initialization function, and on
the user side call a single function that sets up and continuously monitors
the buffers, and writes data to files as it becomes available. Channels
are created when the collection app is started and destroyed when it exits,
not when the kernel module is inserted, so different channel buffer sizes
can be specified for each separate run via command-line options. See the
README in the relay-apps tarball for details.
Also included in the relay-apps tarball are a couple examples
demonstrating how you can use this to create quick and dirty kernel
logging/debugging applications. They are:
- tprintk, short for 'tee printk', which temporarily puts a kprobe on
printk() and writes a duplicate stream of printk output to a relayfs
channel. This could be used anywhere there's printk() debugging code
in the kernel which you'd like to exercise, but would rather not have
your system logs cluttered with debugging junk. You'd probably want
to kill klogd while you do this, otherwise there wouldn't be much
point (since putting a kprobe on printk() doesn't change the output
of printk()). I've used this method to temporarily divert the packet
logging output of the iptables LOG target from the system logs to
relayfs files instead, for instance.
- klog, which just provides a printk-like formatted logging function
on top of relayfs. Again, you can use this to keep stuff out of your
system logs if used in place of printk.
The example applications can be found here:
http://prdownloads.sourceforge.net/dprobes/relay-apps.tar.gz?download
From: Christoph Hellwig <hch@lst.de>
avoid lookup_hash usage in relayfs
Signed-off-by: Tom Zanussi <zanussi@us.ibm.com>
Signed-off-by: Andrew Morton <akpm@osdl.org>
Signed-off-by: Linus Torvalds <torvalds@osdl.org>
2005-09-07 00:16:30 +02:00
|
|
|
*/
|
2006-01-08 10:02:31 +01:00
|
|
|
extern struct file_operations relay_file_operations;
|
[PATCH] relayfs
Here's the latest version of relayfs, against linux-2.6.11-mm2. I'm hoping
you'll consider putting this version back into your tree - the previous
rounds of comment seem to have shaken out all the API issues and the number
of comments on the code itself have also steadily dwindled.
This patch is essentially the same as the relayfs redux part 5 patch, with
some minor changes based on reviewer comments. Thanks again to Pekka
Enberg for those. The patch size without documentation is now a little
smaller at just over 40k. Here's a detailed list of the changes:
- removed the attribute_flags in relay open and changed it to a
boolean specifying either overwrite or no-overwrite mode, and removed
everything referencing the attribute flags.
- added a check for NULL names in relayfs_create_entry()
- got rid of the unnecessary multiple labels in relay_create_buf()
- some minor simplification of relay_alloc_buf() which got rid of a
couple params
- updated the Documentation
In addition, this version (through code contained in the relay-apps tarball
linked to below, not as part of the relayfs patch) tries to make it as easy
as possible to create the cooperating kernel/user pieces of a typical and
common type of logging application, one where kernel logging is kicked off
when a user space data collection app starts and stops when the collection
app exits, with the data being automatically logged to disk in between. To
create this type of application, you basically just include a header file
(relay-app.h, included in the relay-apps tarball) in your kernel module,
define a couple of callbacks and call an initialization function, and on
the user side call a single function that sets up and continuously monitors
the buffers, and writes data to files as it becomes available. Channels
are created when the collection app is started and destroyed when it exits,
not when the kernel module is inserted, so different channel buffer sizes
can be specified for each separate run via command-line options. See the
README in the relay-apps tarball for details.
Also included in the relay-apps tarball are a couple examples
demonstrating how you can use this to create quick and dirty kernel
logging/debugging applications. They are:
- tprintk, short for 'tee printk', which temporarily puts a kprobe on
printk() and writes a duplicate stream of printk output to a relayfs
channel. This could be used anywhere there's printk() debugging code
in the kernel which you'd like to exercise, but would rather not have
your system logs cluttered with debugging junk. You'd probably want
to kill klogd while you do this, otherwise there wouldn't be much
point (since putting a kprobe on printk() doesn't change the output
of printk()). I've used this method to temporarily divert the packet
logging output of the iptables LOG target from the system logs to
relayfs files instead, for instance.
- klog, which just provides a printk-like formatted logging function
on top of relayfs. Again, you can use this to keep stuff out of your
system logs if used in place of printk.
The example applications can be found here:
http://prdownloads.sourceforge.net/dprobes/relay-apps.tar.gz?download
From: Christoph Hellwig <hch@lst.de>
avoid lookup_hash usage in relayfs
Signed-off-by: Tom Zanussi <zanussi@us.ibm.com>
Signed-off-by: Andrew Morton <akpm@osdl.org>
Signed-off-by: Linus Torvalds <torvalds@osdl.org>
2005-09-07 00:16:30 +02:00
|
|
|
|
|
|
|
#endif /* _LINUX_RELAYFS_FS_H */
|
|
|
|
|