mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Anton Altaparmakov <aia21@cam.ac.uk>
To: Andi Kleen <ak@suse.de>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Q: process concurrency and sigaction()
Date: Mon, 09 Apr 2001 13:34:30 +0100	[thread overview]
Message-ID: <5.0.2.1.2.20010409131813.00a68b80@pop.cus.cam.ac.uk> (raw)
In-Reply-To: <20010409134550.A26660@gruyere.muc.suse.de>
In-Reply-To: <5.0.2.1.2.20010409115354.00a311a0@pop.cus.cam.ac.uk> <5.0.2.1.2.20010409115354.00a311a0@pop.cus.cam.ac.uk>

Andi,

Thanks a lot for the explanations! All clear now. (-:

[snip]
At 12:45 09/04/01, Andi Kleen wrote:
>It's ok, but you don't really need to spin. A flag is enough. Also you
>could use the signal blocking function (sigprocmask), but they're slightly
>more expensive than just setting a flag.

Yes, good point. Saves me a whole variable in my data structs in fact, as I 
already have 32 bits worth of mostly unused, atomic flags.

sigprocmask would be rather excessive considering it requires a full 
context switch into the kernel to execute and the high frequency of 
lock/unlocks in the normal code while the handler only executes once every 
5 seconds...

Best regards,

         Anton


-- 
Anton Altaparmakov <aia21 at cam.ac.uk> (replace at with @)
Linux NTFS Maintainer / WWW: http://sourceforge.net/projects/linux-ntfs/
ICQ: 8561279 / WWW: http://www-stu.christs.cam.ac.uk/~aia21/


      parent reply	other threads:[~2001-04-09 12:34 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-04-09 11:32 Anton Altaparmakov
2001-04-09 11:45 ` Andi Kleen
2001-04-09 12:34 ` Anton Altaparmakov [this message]

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=5.0.2.1.2.20010409131813.00a68b80@pop.cus.cam.ac.uk \
    --to=aia21@cam.ac.uk \
    --cc=ak@suse.de \
    --cc=linux-kernel@vger.kernel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

all inboxes | Powered by JetHome®