From: Zach Brown <zab@zabbo.net>
To: kernel-janitors@vger.kernel.org
Subject: Re: [Kernel-janitors] serial.c cli() patch
Date: Thu, 26 Feb 2004 22:59:05 +0000 [thread overview]
Message-ID: <403E7A39.7020703@zabbo.net> (raw)
In-Reply-To: <403D1CC3.6080906@chello.nl>
> Can someone tell me when I do need multiple spinlocks variables instead
> of one global one?
Sometimes it makes more sense to think of the locking as protecting data
instead of paths through code that uses the data. This can get very
complicated depending on the access patterns, of course, but it's a good
way to approach the problem. Look at what promises need to be made to
code that accesses data and see if there is a natural association of
locks with data that will make those promises.
- z
(sorry I don't have specific hints for the serial path)
_______________________________________________
Kernel-janitors mailing list
Kernel-janitors@lists.osdl.org
http://lists.osdl.org/mailman/listinfo/kernel-janitors
next prev parent reply other threads:[~2004-02-26 22:59 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-02-25 22:08 [Kernel-janitors] serial.c cli() patch Debian User
2004-02-25 23:44 ` Debian User
2004-02-25 23:51 ` Debian User
2004-02-26 22:59 ` Zach Brown [this message]
2004-02-26 23:18 ` Matthew Wilcox
2004-02-27 0:32 ` Zach Brown
2004-02-27 15:17 ` Matthew Wilcox
2004-02-28 4:07 ` Arnaldo Carvalho de Melo
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=403E7A39.7020703@zabbo.net \
--to=zab@zabbo.net \
--cc=kernel-janitors@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 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.