Re: [RFC] maximum latency tracking infrastructure (version 2)

[Alexey Dobriyan]

On Fri, Aug 25, 2006 at 01:22:19PM +0200, Arjan van de Ven wrote:
> --- /dev/null
> +++ linux-2.6.18-rc4-latency/include/linux/latency.h

> +#ifdef __KERNEL__

Since you haven't added it to list of exported headers, this is
unneeded.

> +#ifndef _INCLUDE_GUARD_LATENCY_H_
> +#define _INCLUDE_GUARD_LATENCY_H_
> +
> +#include <linux/notifier.h>

Just
	struct notifier_block;

> +void set_acceptable_latency(char *identifier, int usecs);
> +void modify_acceptable_latency(char *identifier, int usecs);
> +void remove_acceptable_latency(char *identifier);
> +void synchronize_acceptable_latency(void);
> +int system_latency_constraint(void);
> +
> +int register_latency_notifier(struct notifier_block * nb);
> +int unregister_latency_notifier(struct notifier_block * nb);
> +
> +#define INFINITE_LATENCY 1000000
> +
> +#endif
> +#endif

> --- linux-2.6.18-rc4-latency.orig/kernel/Makefile
> +++ linux-2.6.18-rc4-latency/kernel/Makefile
> @@ -8,7 +8,7 @@ obj-y     = sched.o fork.o exec_domain.o
>  	    signal.o sys.o kmod.o workqueue.o pid.o \
>  	    rcupdate.o extable.o params.o posix-timers.o \
>  	    kthread.o wait.o kfifo.o sys_ni.o posix-cpu-timers.o mutex.o \
> -	    hrtimer.o rwsem.o
> +	    hrtimer.o rwsem.o latency.o

CONFIG_PM=n users aren't interested, right?

-
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/