Coccinelle Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: elfring@users.sourceforge.net (SF Markus Elfring)
To: cocci@systeme.lip6.fr
Subject: [Cocci] release: 1.0.2: Software evolution around parallelisation support
Date: Sun, 23 Aug 2015 22:20:31 +0200	[thread overview]
Message-ID: <55DA2B0F.9080006@users.sourceforge.net> (raw)
In-Reply-To: <alpine.DEB.2.10.1508231227480.2916@hadrien>

> There is no shared memory in ocaml.

Specific services (like databases) can provide some shared data storage.


> initialize and finalize naturally suggest that locations created in initialize
> can all be collected in a single execution of finalize. Since this is not possible,

I imagine that these SmPL rules could still be supported for their
original purpose.


> initialize and finalize are not allowed.

It might be easier for a moment to exclude these components under the
constraints of limited software development resources.
Such limitations will result in some software development challenges,
won't it?


> If you are OK with disjoint memory spaces per thread,
> just use the existing script for parallelism.

How do you think about the potential for extensions around task-specific
preparation and clean-up?


>> Does the parallelisation support need any more fine-tuning?
>> * How often is task preparation required before further data processing
>>   can be performed in parallel?
>>
>> * Which programming interfaces do you prefer for the storage
>>   of collected data in the fork-join work flow?
> No idea what either of these questions mean, but the whole point is that
> there is no join.

This technical restriction can lead to data processing difficulties,
can't it?

Are there any situations where SmPL scripts will need more control about
parallel work?

Regards,
Markus

  reply	other threads:[~2015-08-23 20:20 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-08-22 14:09 [Cocci] 1.0.2 Julia Lawall
2015-08-23 17:47 ` [Cocci] release: 1.0.2: Better file selection SF Markus Elfring
2015-08-23 18:16 ` [Cocci] release: 1.0.2: Software evolution around parallelisation support SF Markus Elfring
2015-08-23 19:30   ` Julia Lawall
2015-08-23 20:20     ` SF Markus Elfring [this message]
2015-08-25  6:42     ` SF Markus Elfring
2015-08-25  6:54       ` Julia Lawall
2015-08-25  7:20         ` SF Markus Elfring
2015-08-26  5:50     ` SF Markus Elfring
2015-08-26  9:11       ` Julia Lawall
2015-08-26 10:43         ` SF 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=55DA2B0F.9080006@users.sourceforge.net \
    --to=elfring@users.sourceforge.net \
    --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