LinuxPPC-Dev Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: "Srinivas Murthy" <codevana@gmail.com>
To: linuxppc-dev <linuxppc-dev@ozlabs.org>
Subject: Synch question 2.6.x
Date: Mon, 19 Jun 2006 20:10:19 -0700	[thread overview]
Message-ID: <7cb1293c0606192010o1c4ebbdfw3719fcef8dcefd94@mail.gmail.com> (raw)

[-- Attachment #1: Type: text/plain, Size: 684 bytes --]

Hi,
 I have this 2.6.x kernel mode component for which I have question regarding
the synch reqmt. between workqueues (or tasklets) and kernel threads. The
kernel threads are created from within the kernel module and there is no
user-mode side to them.

 I share some global data in the kernel space that is accessed by the kernel
thread and a work queue (or a tasklet) (kicked off of an isr top-half and
also off of a kernel thread).

 Is there a need to synch access to this data if the preemption is off. What
if the premption is turned on?

 In the case of workq's, if the synch is reqd, are down_xx() up_xx(),
primitives the right ones to use?

Thanks much in advance.

_Srinivas

[-- Attachment #2: Type: text/html, Size: 932 bytes --]

                 reply	other threads:[~2006-06-20  3:10 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=7cb1293c0606192010o1c4ebbdfw3719fcef8dcefd94@mail.gmail.com \
    --to=codevana@gmail.com \
    --cc=linuxppc-dev@ozlabs.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