Ò׽ؽØͼÈí¼þ¡¢µ¥Îļþ¡¢Ãâ°²×°¡¢´¿ÂÌÉ«¡¢½ö160KB

LinuxµÄ¹¤×÷¶ÓÁÐ

1£¬ÏÈ¿´¿´¹¤×÷¶ÓÁкÍtaskletµÄÇø±ð£º
    £¨1£© ¶¨Ê±Æ÷ºÍtasklet£º
    Tasklets resemble kernel timers in 3 ways.
      1)They are always run at interrupt time,
      2)they always run on the same CPU that schedules them,
      3)and they receive an unsigned long argument.   Unlike kernel timers, however, you can’t ask to execute the function at a specific time.
     £¨2£© taskletºÍ¹¤×÷¶ÓÁУº
     Workqueues are, superficially, similar to tasklets; they allow kernel code to request that a function be called at some future time. There are, however, some significant differences between the two, including:
        1) Tasklets run in software interrupt context with the result that all tasklet code must be atomic. Instead, workqueue functions run in the context of a special kernel process; as a result, they have more flexibility. In particular, workqueue functions can sleep.
        2)Tasklets always run on the processor from which they were originally submitted. Workqueues work in the same way, by default.
        3)Kernel code can request that the execution of workqueue functions be delayed for an explicit interval.
2£¬¹¤×÷¶ÓÁÐ(work queue)ÊÇLinux kernelÖн«¹¤×÷ÍƺóÖ´ÐеÄÒ»ÖÖ»úÖÆ¡£ÕâÖÖ»úÖƺÍBH»òTasklets²»Í¬Ö®´¦ÔÚÓÚ¹¤×÷¶ÓÁÐÊÇ°ÑÍƺóµÄ¹¤×÷½»ÓÉÒ»¸öÄÚºËÏß³ÌÈ¥Ö´ÐУ¬Òò´Ë¹¤×÷¶ÓÁеÄÓÅÊƾÍÔÚÓÚËüÔÊÐíÖØе÷¶ÈÉõÖÁ˯Ãß¡£¹¤×÷¶ÓÁÐÊÇ2.6Äں˿ªÊ¼ÒýÈëµÄ»úÖÆ£¬ÔÚ2.6.20Ö®ºó£¬¹¤×÷¶ÓÁеÄÊý¾Ý½á¹¹·¢ÉúÁËһЩ±ä»¯£¬Òò´Ë±¾ÎÄ·Ö³ÉÁ½¸ö²¿·Ö¶Ô2.6.20֮ǰºÍÖ®ºóµÄ°æ±¾·Ö±ð×ö½éÉÜ¡£
    £¨1£©2.6.0~2.6.19
Êý¾Ý½á¹¹£º
struct work_struct {
    unsigned long pending;
    struct list_head entry;
    void (*func)(void *);
    void *data


Ïà¹ØÎĵµ£º

Moto LinuxÓ¦Óÿª·¢£¨Áù£©£ºUSBÁ¬½Ó¹²ÏíPCÉÏÍø

ÓÉÓÚÔÚ¿ª·¢A1200ÉϵÄÁ÷ýÌå²¥·ÅÆ÷£¬Ãâ²»Á˳¤ÆÚ²¥·ÅÊÓƵ£¬½øÐÐÎȶ¨ÐÔ²âÊÔ¡£¿ªÊ¼ÊÇͨ¹ýGPRS²¦ºÅÉÏÍø£¬µ«²¥·ÅÊÓƵ̫·ÑÁ÷Á¿ÁË£¬³ä¸ö50Ôª£¬¶¼¶¥²»×¡Ò»ÌìµÄ²âÊÔ¡£¿´µ½window mobileµÄÊÖ»ú¶¼¿ÉÒÔͨ¹ýPCÉÏÍø£¬Òò´ËÏëµ½moto linuxÊÖ»úÒ²¿ÉÒÔ¹²ÏíPCÉÏÍø£¬½ÚÊ¡Á÷Á¿·ÑÓᣴÓÀíÂÛÉϽ«ÊÇ¿ÉÐеģ¬ÒòΪmotoÊÖ»ú¿ÉÒÔ¿ªÆôUSB LAN£¬Í¨¹ýUSBÁ¬½Ó ......

Linuxϵͳ°²×°Ö®¶þ: Ó²ÅÌ°²×°Fedora 9

ÈÈÐĵãÆÀ£ºÓ²ÅÌ°²×°fedoraµÄ¹æÔò¾ÍÏñÎÒÃǷdz£ÑÇ¿ËÎ÷µÄÕþ²ßÒ»Ñù£¬ ¸æËßÄã²»ÄÜ·¢ËÍyellow¶ÌÐÅ£¬ µ«¾ÍÊDz»¸æËßÄãyellowµÄ³ß¶ÈÊÇʲô£¬ ÄãÖ»ÄÜð×ÅÊÖ»úÍ£»úµÄΣÏÕ£¬²âÊÔÏÂÄÄЩ¶ÌО¿¾¹Éä»ÆÁË¡£ ͨ¹ý²»ÏÂÁ½Î»ÊýµÄÖØÆô£¬ ÃþË÷ÁËÒ»µãµã¹æÔò¡£ OK, ÎÒÏëLinux²»ÊÇgov, °²×°»¹ÊÇÓйæÔò¿ÉÑԵģ¬Ö»ÊÇÎÒÃÇ»¹Ã»ÓÐÕÒµ½Õâ¸öreadme?  ´ï ......

How to check into Linux OS

I learned some experience while Nanjing found 0x03 error. At begining, we don't know why our GSRM(a linux process) hang in a short time 5 seconds sometimes. It didn't handle any message at that time and the interruption is not regularly. So we assume we have Linux OS problem. We did following checks ......

Linux»·¾³½ø³Ì¼äͨÐÅ


Linux»·¾³½ø³Ì¼äͨÐÅ£¨Ò»£©
¹ÜµÀ¼°ÓÐÃû¹ÜµÀ
Ö£ÑåÐË (mlinux@163.com)¹ú·À¿Æ´ó¼ÆËã»úѧԺ
2002 Äê 12 ÔÂ 11 ÈÕ
ÔÚ±¾ÏµÁÐÐòÖÐ×÷Õ߸ÅÊöÁË linux ½ø³Ì¼äͨÐŵļ¸ÖÖÖ÷ÒªÊֶΡ£ÆäÖйܵÀºÍÓÐÃû¹ÜµÀÊÇ×îÔçµÄ½ø³Ì¼äͨÐÅ»úÖÆÖ®Ò»£¬¹ÜµÀ¿ÉÓÃÓÚ¾ßÓÐÇ×Ôµ¹Øϵ½ø³Ì¼äµÄͨÐÅ£¬ÓÐÃû¹ÜµÀ¿Ë·þÁ˹ܵÀûÓÐÃû×ÖµÄÏÞÖÆ£¬Òò´Ë£¬³ý¾ßÓйܵ ......
© 2009 ej38.com All Rights Reserved. ¹ØÓÚE½¡ÍøÁªÏµÎÒÃÇ | Õ¾µãµØͼ | ¸ÓICP±¸09004571ºÅ