From: "Leonidas ." <leonidas137@gmail.com>
To: Valdis.Kletnieks@vt.edu
Cc: linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: Can current macro be accessed from interrupt context?
Date: Thu, 22 Oct 2009 23:42:08 +0530 [thread overview]
Message-ID: <f22d86810910221112x75a908eewe015eb5eae883aa9@mail.gmail.com> (raw)
In-Reply-To: <f22d86810910221046l366d3017r8b8823e4750ffea2@mail.gmail.com>
Assumption
> here is a certain task can be in kernel mode only on one cpu at a time
> hence that task specific
> data structure can be accessed without locks.
This is pretty much like per cpu variables, right? Conceptually there
is no difference
in per-cpu mechanism and what I am thinking.
-Leo.
next prev parent reply other threads:[~2009-10-22 18:17 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-10-22 11:10 Leonidas .
2009-10-22 11:27 ` Frederic Weisbecker
2009-10-22 11:43 ` Leonidas .
2009-10-22 11:49 ` Leonidas .
2009-10-22 12:06 ` Frederic Weisbecker
2009-10-22 13:37 ` Leonidas .
2009-10-22 13:45 ` Arjan van de Ven
2009-10-22 15:17 ` Valdis.Kletnieks
2009-10-22 17:46 ` Leonidas .
2009-10-22 18:12 ` Leonidas . [this message]
2009-10-23 8:13 ` Clemens Ladisch
2009-10-23 9:34 ` Leonidas .
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=f22d86810910221112x75a908eewe015eb5eae883aa9@mail.gmail.com \
--to=leonidas137@gmail.com \
--cc=Valdis.Kletnieks@vt.edu \
--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®