Re: [patch] Real-Time Preemption, -RT-2.6.11-rc2-V0.7.36-00
EFS_FS is not set # CONFIG_BFS_FS is not set # CONFIG_EFS_FS is not set # CONFIG_CRAMFS is not set # CONFIG_VXFS_FS is not set # CONFIG_HPFS_FS is not set # CONFIG_QNX4FS_FS is not set # CONFIG_SYSV_FS is not set # CONFIG_UFS_FS is not set # # Network File Systems # # CONFIG_NFS_FS is not set # CONFIG_NFSD is not set # CONFIG_EXPORTFS is not set # CONFIG_SMB_FS is not set # CONFIG_CIFS is not set # CONFIG_NCP_FS is not set # CONFIG_CODA_FS is not set # CONFIG_AFS_FS is not set # # Partition Types # # CONFIG_PARTITION_ADVANCED is not set CONFIG_MSDOS_PARTITION=y # # Native Language Support # CONFIG_NLS=y CONFIG_NLS_DEFAULT="iso8859-1" CONFIG_NLS_CODEPAGE_437=y # CONFIG_NLS_CODEPAGE_737 is not set # CONFIG_NLS_CODEPAGE_775 is not set # CONFIG_NLS_CODEPAGE_850 is not set # CONFIG_NLS_CODEPAGE_852 is not set # CONFIG_NLS_CODEPAGE_855 is not set # CONFIG_NLS_CODEPAGE_857 is not set # CONFIG_NLS_CODEPAGE_860 is not set # CONFIG_NLS_CODEPAGE_861 is not set # CONFIG_NLS_CODEPAGE_862 is not set # CONFIG_NLS_CODEPAGE_863 is not set # CONFIG_NLS_CODEPAGE_864 is not set # CONFIG_NLS_CODEPAGE_865 is not set # CONFIG_NLS_CODEPAGE_866 is not set # CONFIG_NLS_CODEPAGE_869 is not set # CONFIG_NLS_CODEPAGE_936 is not set # CONFIG_NLS_CODEPAGE_950 is not set # CONFIG_NLS_CODEPAGE_932 is not set # CONFIG_NLS_CODEPAGE_949 is not set # CONFIG_NLS_CODEPAGE_874 is not set # CONFIG_NLS_ISO8859_8 is not set # CONFIG_NLS_CODEPAGE_1250 is not set # CONFIG_NLS_CODEPAGE_1251 is not set # CONFIG_NLS_ASCII is not set CONFIG_NLS_ISO8859_1=y # CONFIG_NLS_ISO8859_2 is not set # CONFIG_NLS_ISO8859_3 is not set # CONFIG_NLS_ISO8859_4 is not set # CONFIG_NLS_ISO8859_5 is not set # CONFIG_NLS_ISO8859_6 is not set # CONFIG_NLS_ISO8859_7 is not set # CONFIG_NLS_ISO8859_9 is not set # CONFIG_NLS_ISO8859_13 is not set # CONFIG_NLS_ISO8859_14 is not set # CONFIG_NLS_ISO8859_15 is not set # CONFIG_NLS_KOI8_R is not set # CONFIG_NLS_KOI8_U is not set # CONFIG_NLS_UTF8 is not set # # Profiling support # # CONFIG_PROFILING is not set # # Kernel hacking # # CONFIG_DEBUG_KERNEL is not set # CONFIG_DEBUG_PREEMPT is not set CONFIG_WAKEUP_TIMING=y # CONFIG_CRITICAL_PREEMPT_TIMING is not set # CONFIG_CRITICAL_IRQSOFF_TIMING is not set CONFIG_LATENCY_TIMING=y # CONFIG_LATENCY_TRACE is not set CONFIG_RT_DEADLOCK_DETECT=y # CONFIG_DEBUG_BUGVERBOSE is not set # CONFIG_USE_FRAME_POINTER is not set CONFIG_EARLY_PRINTK=y CONFIG_4KSTACKS=y CONFIG_X86_FIND_SMP_CONFIG=y CONFIG_X86_MPPARSE=y # # Security options # # CONFIG_KEYS is not set # CONFIG_SECURITY is not set # # Cryptographic options # # CONFIG_CRYPTO is not set # # Hardware crypto devices # # # Library routines # # CONFIG_CRC_CCITT is not set CONFIG_CRC32=y CONFIG_LIBCRC32C=m CONFIG_GENERIC_HARDIRQS=y CONFIG_GENERIC_IRQ_PROBE=y CONFIG_X86_SMP=y CONFIG_X86_HT=y CONFIG_X86_BIOS_REBOOT=y CONFIG_X86_TRAMPOLINE=y On Sun, 23 Jan 2005 09:40:56 -0500, Gene Heskett <[EMAIL PROTECTED]> wrote: > On Sunday 23 January 2005 06:31, Ingo Molnar wrote: > >* andyliu <[EMAIL PROTECTED]> wrote: > >> hi , ingo > >> > >> i am trying to understand your patch,but the patch file is so long > >> and complex. i am wondering is there some documents about your > >> patch? > >> > >> :) > > > >well, it mainly offers the PREEMPT_RT feature, which is a 'no > >compromises' variant of kernel preemption: virtually everything > >(including normal spinlocked sections) is preemptable, with the goal > > of providing hard-realtime category ~10-20 usecs maximum scheduling > > latency guarantees on a typical PC (or embedded platform). Those > > long and complex changes are almost all needed to achieve this > > goal. > > > >this tree is mainly an experiment to see what it takes to achieve > > that latency goal, and to see how much of that can go upstream > > (without having to decide whether upstream wants to have the > > PREEMPT_RT feature or not). (A couple of dozen patches were already > > split out of this patch and are in the current upstream kernel - > > they already made a latency difference for the 2.6.10 kernel.) > > > > Ingo > > Hijacking the thread here Ingo, but did you see my build failure > message of yesterday? > > -- > Cheers, Gene > "There are four boxes to be used in defense of liberty: > soap, ballot, jury, and ammo. Please use in that order." > -Ed Howdershelt (Author) > 99.32% setiathome rank, not too shabby for a WV hillbilly > Yahoo.com attorneys please note, additions to this message > by Gene Heskett are: > Copyright 2005 by Maurice Eugene Heskett, all rights reserved. > -- Yours andyliu - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: [2.6 patch] loop.c: make two functions static
hi, adrian
i always see patches which set functions and variables to static.
what's the main difference between static and non-static things?
On Sun, 23 Jan 2005 11:17:10 +0100, Adrian Bunk <[EMAIL PROTECTED]> wrote:
> This patch makes two needlessly global functions static.
>
> Signed-off-by: Adrian Bunk <[EMAIL PROTECTED]>
>
> ---
>
> drivers/block/loop.c |4 ++--
> 1 files changed, 2 insertions(+), 2 deletions(-)
>
> This patch was already sent on:
> - 29 Nov 2004
>
> --- linux-2.6.10-rc1-mm3-full/drivers/block/loop.c.old 2004-11-06
> 20:09:10.0 +0100
> +++ linux-2.6.10-rc1-mm3-full/drivers/block/loop.c 2004-11-06
> 20:09:31.0 +0100
> @@ -1114,7 +1114,7 @@
> EXPORT_SYMBOL(loop_register_transfer);
> EXPORT_SYMBOL(loop_unregister_transfer);
>
> -int __init loop_init(void)
> +static int __init loop_init(void)
> {
> int i;
>
> @@ -1189,7 +1189,7 @@
> return -ENOMEM;
> }
>
> -void loop_exit(void)
> +static void loop_exit(void)
> {
> int i;
>
> -
> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> the body of a message to [EMAIL PROTECTED]
> More majordomo info at http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at http://www.tux.org/lkml/
>
--
Yours andyliu
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Re: [patch] Real-Time Preemption, -RT-2.6.11-rc2-V0.7.36-00
hi , ingo i am trying to understand your patch,but the patch file is so long and complex. i am wondering is there some documents about your patch? :) thanks very much for your patch and your work. On Sat, 22 Jan 2005 16:22:24 -0500, Gene Heskett <[EMAIL PROTECTED]> wrote: > On Saturday 22 January 2005 07:29, Ingo Molnar wrote: > >i have released the -V0.7.36-00 Real-Time Preemption patch, which > > can be downloaded from the usual place: > > > > http://redhat.com/~mingo/realtime-preempt/ > > > >this is mainly a merge to 2.6.11-rc2. > > Humm, by the time I went after the patch it was up to -02. > > And I'm getting a couple of error exits: > --- > net/sched/sch_generic.c: In function `qdisc_restart': > net/sched/sch_generic.c:128: error: label `requeue' used but not > defined > CC drivers/pci/setup-bus.o > make[2]: *** [net/sched/sch_generic.o] Error 1 > make[1]: *** [net/sched] Error 2 > make[1]: *** Waiting for unfinished jobs > --- > > And > --- > LD net/sunrpc/built-in.o > make: *** [net] Error 2 > make: *** Waiting for unfinished jobs > --- > So obviously I'm not running it. :-) > > One other item I don't think is related, in the last version (35-01) I > had svn'd a new ieee1396 sub-directory from that ieee1394.org site > into the drivers tree, and since it was less than a week old and > worked right well, I just copied it over into the new kernel tree & > reran the configs after renameing the existing ieee1394 to > ieee1394-orig. > > >There was alot of merging to be done due to Thomas Gleixner's > >spinlock/rwlock cleanups making it into upstream and due to the > > upstream spinlock changes, and there were some networking related > > conflicts as well, so these areas might introduce new regressions. > > > >the patch includes a fix that should resolve the microcode-update > >related boot-time crash reported by K.R. Foley. It also includes a > >verify_mm_writelocked() fix from Daniel Walker. > > > >to create a -V0.7.36-00 tree from scratch, the patching order is: > > > > http://kernel.org/pub/linux/kernel/v2.6/linux-2.6.10.tar.bz2 > > > > http://kernel.org/pub/linux/kernel/v2.6/testing/patch-2.6.11-rc2.bz > >2 > > http://redhat.com/~mingo/realtime-preempt/realtime-preempt-2.6.11-r > >c2-V0.7.36-00 > > > > Ingo > > -- > Cheers, Gene > "There are four boxes to be used in defense of liberty: > soap, ballot, jury, and ammo. Please use in that order." > -Ed Howdershelt (Author) > 99.32% setiathome rank, not too shabby for a WV hillbilly > Yahoo.com attorneys please note, additions to this message > by Gene Heskett are: > Copyright 2005 by Maurice Eugene Heskett, all rights reserved. > - > To unsubscribe from this list: send the line "unsubscribe linux-kernel" in > the body of a message to [EMAIL PROTECTED] > More majordomo info at http://vger.kernel.org/majordomo-info.html > Please read the FAQ at http://www.tux.org/lkml/ > -- Yours andyliu - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
