From mboxrd@z Thu Jan 1 00:00:00 1970 From: bmeneguele@gmail.com (Bruno E. O. Meneguele) Date: Thu, 16 Nov 2017 11:34:39 -0200 Subject: sleep In-Reply-To: References: <20171026001203.GD12341@eros> <20171114165206.GA3805@glitch> Message-ID: <20171116133439.GA8089@glitch> To: kernelnewbies@lists.kernelnewbies.org List-Id: kernelnewbies.lists.kernelnewbies.org On 14-11, Max Filippov wrote: > On Tue, Nov 14, 2017 at 8:52 AM, Bruno E. O. Meneguele > wrote: > > What > > confused me for sometime was the 'atomic' vs 'interrupt' naming, but > > after reading Robert's book it cames to the fact that they're the same. > > Not exactly the same. Atomic means you're protected from some sort of > interruption: e.g. you raise preemption counter and you're protected from > scheduling, but you still may be interrupted, or you disable interrupts and > you're protected from scheduling and interrupts, but there still may be an > NMI. > Ahh, well pointed. Got it. Thank you for the info :) -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 488 bytes Desc: not available Url : http://lists.kernelnewbies.org/pipermail/kernelnewbies/attachments/20171116/ab20746b/attachment.bin