public inbox for ltp@lists.linux.it
 help / color / mirror / Atom feed
From: chrubis@suse.cz
To: Alexey Kodanev <alexey.kodanev@oracle.com>
Cc: vasily.isaenko@oracle.com, ltp-list@lists.sourceforge.net,
	Mike Frysinger <vapier@gentoo.org>
Subject: Re: [LTP] [PATCH] lib/tst_res.c: synchronize access to tst_res functions
Date: Tue, 25 Feb 2014 14:19:32 +0100	[thread overview]
Message-ID: <20140225131932.GB13201@rei> (raw)
In-Reply-To: <1392731616-25514-1-git-send-email-alexey.kodanev@oracle.com>

Hi!
> The patch adds synchronization mechanism which is required (tst_res.c
> uses global variables e.g. T_exitval, tst_count, T_out, ...) when tst_res
> functions are used in multi-threaded tests.
> Note: it will only work if test is linked with pthread library, also some
> functions include each other that is why recursive mutex is used (can be
> locked several times by the same thread).

This looks good to me.

Mike can you have a look, just to be extra sure.

-- 
Cyril Hrubis
chrubis@suse.cz

------------------------------------------------------------------------------
Flow-based real-time traffic analytics software. Cisco certified tool.
Monitor traffic, SLAs, QoS, Medianet, WAAS etc. with NetFlow Analyzer
Customize your own dashboards, set traffic alerts and generate reports.
Network behavioral analysis & security monitoring. All-in-one tool.
http://pubads.g.doubleclick.net/gampad/clk?id=126839071&iu=/4140/ostg.clktrk
_______________________________________________
Ltp-list mailing list
Ltp-list@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/ltp-list

  reply	other threads:[~2014-02-25 13:19 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-02-18 13:53 [LTP] [PATCH] lib/tst_res.c: synchronize access to tst_res functions Alexey Kodanev
2014-02-25 13:19 ` chrubis [this message]
2014-03-11 15:11   ` chrubis
2014-03-24 17:11 ` chrubis

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=20140225131932.GB13201@rei \
    --to=chrubis@suse.cz \
    --cc=alexey.kodanev@oracle.com \
    --cc=ltp-list@lists.sourceforge.net \
    --cc=vapier@gentoo.org \
    --cc=vasily.isaenko@oracle.com \
    /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