cocci.inria.fr archive mirror
 help / color / mirror / Atom feed
From: Markus Elfring <Markus.Elfring@web.de>
To: Coccinelle <cocci@systeme.lip6.fr>
Subject: [Cocci] Rejecting parallel execution of SmPL scripts
Date: Wed, 24 Apr 2019 08:25:58 +0200	[thread overview]
Message-ID: <0ce0ec2b-e3df-bb0e-ee75-066f5ff71154@web.de> (raw)
In-Reply-To: <bed744fe-5c5c-cf28-f8b2-40a487709010@web.de>

Hello,

The Coccinelle software supports multi-processing (parameter “--jobs”)
for a while. It would be occasionally useful to share data between started
(background) processes for specific analysis tasks.
Such parallel data collection would require a software design which is safe
for data synchronisation.

The information “Database connections generally do not travel across
process boundaries.” is provided by a known software documentation.
https://docs.sqlalchemy.org/en/13/core/connections.html#engine-disposal

It was determined once more then that transaction management does only work
within a single process by this programming interface so far.
https://groups.google.com/d/msg/sqlalchemy/5-6O-Pwzh4A/5xSnxE_pDAAJ


I got information like the following (on 2018-05-12).

@initialize:ocaml@
@@
let _ =
  if not (!Flag.parmap_cores = None) then failwith "bad"


It seems that I did not become familiar enough with the programming
language “OCaml” to integrate another check (in a convenient way) for
the special case that the parameter “-j 1” could be passed.
(Related system constraints can be also interesting.)

Would you like to help a bit more to achieve the restriction for
serial execution of selected SmPL scripts?

Regards,
Markus
_______________________________________________
Cocci mailing list
Cocci@systeme.lip6.fr
https://systeme.lip6.fr/mailman/listinfo/cocci

  parent reply	other threads:[~2019-04-24  6:26 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-04-20 18:50 [Cocci] Checking import of code search results into a table by parallel SmPL data processing Markus Elfring
     [not found] ` <alpine.DEB.2.21.1904202112150.2499@hadrien>
2019-04-20 19:31   ` Markus Elfring
2019-04-23  9:48   ` Markus Elfring
2019-04-24  6:25 ` Markus Elfring [this message]
2019-04-25  8:06 ` [Cocci] Data exchange over network interfaces by SmPL scripts Markus Elfring
     [not found]   ` <alpine.DEB.2.21.1904251039000.2550@hadrien>
2019-04-25 10:32     ` Markus Elfring
2019-04-27 17:20       ` Markus Elfring
2019-04-27 17:24       ` Markus Elfring
2019-04-30  8:55         ` Markus Elfring
2019-06-01 11:13         ` Markus Elfring
2019-04-25 18:12 ` [Cocci] Data exchange through message queue " Markus Elfring

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=0ce0ec2b-e3df-bb0e-ee75-066f5ff71154@web.de \
    --to=markus.elfring@web.de \
    --cc=cocci@systeme.lip6.fr \
    /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 NNTP newsgroup(s).