It forces read and write operations to take place before proceeding further. (during optimization, compiler may not perform read and write immediately). Regards Mohanlal ----- Original Message ----- From: "manish regmi" <manish_regmi@hotmail.com> To: <kernelnewbies@nl.linux.org> Sent: Thursday, June 24, 2004 10:36 AM Subject: kernel preemption > Hi, > Can anybody explain me what is barrier() doing in preempt_enable() and > preempt_disable(). > I saw it is a macro expanding to __memory_barrier(). What does it do? > > Also, When can kernel preempt. ie. preempt_count is 1. > > thanks > > _________________________________________________________________ > The new MSN 8: smart spam protection and 2 months FREE* > http://join.msn.com/?page=features/junkmail > > > -- > Kernelnewbies: Help each other learn about the Linux kernel. > Archive: http://mail.nl.linux.org/kernelnewbies/ > FAQ: http://kernelnewbies.org/faq/ > > -- Kernelnewbies: Help each other learn about the Linux kernel. Archive: http://mail.nl.linux.org/kernelnewbies/ FAQ: http://kernelnewbies.org/faq/
