From: bmeneguele@gmail.com (Bruno E. O. Meneguele)
To: kernelnewbies@lists.kernelnewbies.org
Subject: sleep
Date: Thu, 16 Nov 2017 11:34:39 -0200 [thread overview]
Message-ID: <20171116133439.GA8089@glitch> (raw)
In-Reply-To: <CAMo8Bf+CKKN_2EJT2w_bTH17EqXErsaJcYQSxj_ipBrT=O=wfA@mail.gmail.com>
On 14-11, Max Filippov wrote:
> On Tue, Nov 14, 2017 at 8:52 AM, Bruno E. O. Meneguele
> <bmeneguele@gmail.com> 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
next prev parent reply other threads:[~2017-11-16 13:34 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-10-26 0:12 sleep Tobin C. Harding
2017-10-28 12:41 ` sleep Bogdan Lazic
2017-11-14 16:52 ` sleep Bruno E. O. Meneguele
2017-11-14 20:41 ` sleep Tobin C. Harding
2017-11-14 20:53 ` sleep Max Filippov
2017-11-16 13:34 ` Bruno E. O. Meneguele [this message]
-- strict thread matches above, loose matches on Subject: below --
2002-10-03 1:48 Sleep linuxguruguy
2002-10-04 2:05 ` Sleep William Lee Irwin III
2002-10-04 2:26 ` Sleep Andrew Morton
2002-10-04 5:39 ` Sleep Gerrit Huizenga
2002-10-07 13:54 ` Sleep Bernd Petrovitsch
2002-10-04 3:15 ` Sleep Joe Kellner
2002-10-04 8:07 ` Sleep jbradford
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20171116133439.GA8089@glitch \
--to=bmeneguele@gmail.com \
--cc=kernelnewbies@lists.kernelnewbies.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.