All of lore.kernel.org
 help / color / mirror / Atom feed
From: DEGREMONT Aurelien <aurelien.degremont@cea.fr>
To: lustre-devel@lists.lustre.org
Subject: [Lustre-devel] llog API, locking and concurrency
Date: Wed, 06 Apr 2011 18:58:47 +0200	[thread overview]
Message-ID: <4D9C9BC7.5050603@cea.fr> (raw)

Hello

I'm wondering what is the correct way to use llog_ API regarding locking 
and concurrencies?

When looking at code, it seems llog already deal with proper locking 
when several thread access the same llog.
The codes that use this king of log do not seem to add more locking when 
using it.

Is this correct? llog_* call can be called without taking care of 
concurrency?


Thanks

Aur?lien

             reply	other threads:[~2011-04-06 16:58 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-04-06 16:58 DEGREMONT Aurelien [this message]
2011-04-06 17:33 ` [Lustre-devel] llog API, locking and concurrency Alex Zhuravlev

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=4D9C9BC7.5050603@cea.fr \
    --to=aurelien.degremont@cea.fr \
    --cc=lustre-devel@lists.lustre.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.