public inbox for ecos-discuss@sourceware.org
 help / color / mirror / Atom feed
From: Andrew Lunn <andrew@lunn.ch>
To: fazio@planetek.it
Cc: ecos-discuss@sources.redhat.com
Subject: Re: [ECOS] thread & resources lock
Date: Fri, 12 Dec 2003 11:36:00 -0000	[thread overview]
Message-ID: <20031212103232.GB1192@lunn.ch> (raw)
In-Reply-To: <3FD995E3.3661.52D26A5@localhost>

On Fri, Dec 12, 2003 at 10:18:11AM +0100, fazio@planetek.it wrote:

> I have a doubt about resouces management used by two threads: one
> thread writes a variable and the other one reads its content. Do I
> have to lock the resource only when I write it or both in writing
> and reading?

I suggest you find a good book about multi-threaded programming and
operating systems. It should cover thinks like this. You need to
understand the background before you look at your specific problem.

        Andrew

-- 
Before posting, please read the FAQ: http://sources.redhat.com/fom/ecos
and search the list archive: http://sources.redhat.com/ml/ecos-discuss

      reply	other threads:[~2003-12-12 10:35 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-12-12  9:35 fazio
2003-12-12 11:36 ` Andrew Lunn [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=20031212103232.GB1192@lunn.ch \
    --to=andrew@lunn.ch \
    --cc=ecos-discuss@sources.redhat.com \
    --cc=fazio@planetek.it \
    /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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).