From: SF Markus Elfring <elfring@users.sourceforge.net>
To: Julia Lawall <julia.lawall@lip6.fr>
Cc: "Luis R. Rodriguez" <mcgrof@suse.com>,
Johannes Berg <johannes@sipsolutions.net>,
linux-kernel@vger.kernel.org, backports@vger.kernel.org,
cocci@systeme.lip6.fr
Subject: Re: [Cocci] [PATCH] coccinelle: add pycocci wrapper for multithreaded support
Date: Fri, 11 Apr 2014 08:15:11 +0200 [thread overview]
Message-ID: <5347886F.8070307@users.sourceforge.net> (raw)
In-Reply-To: <alpine.DEB.2.02.1404110800120.2032@localhost6.localdomain6>
>> Could you find out during the data processing which parts or files
>> result in a special application behaviour you would like to point out here?
> I don't understand the question at all, but since the various files have
> different properties, it is hard to determine automatically in advance how
> much work Coccinelle will need to do on each one.
It was reported that a system utilisation did not fit to some
expectations. I am curious if any more details or patterns can be
determined for an observed situation.
Do the involved files need also another look?
- semantic patches
- source directories
Regards,
Markus
WARNING: multiple messages have this Message-ID (diff)
From: elfring@users.sourceforge.net (SF Markus Elfring)
To: cocci@systeme.lip6.fr
Subject: [Cocci] [PATCH] coccinelle: add pycocci wrapper for multithreaded support
Date: Fri, 11 Apr 2014 08:15:11 +0200 [thread overview]
Message-ID: <5347886F.8070307@users.sourceforge.net> (raw)
In-Reply-To: <alpine.DEB.2.02.1404110800120.2032@localhost6.localdomain6>
>> Could you find out during the data processing which parts or files
>> result in a special application behaviour you would like to point out here?
> I don't understand the question at all, but since the various files have
> different properties, it is hard to determine automatically in advance how
> much work Coccinelle will need to do on each one.
It was reported that a system utilisation did not fit to some
expectations. I am curious if any more details or patterns can be
determined for an observed situation.
Do the involved files need also another look?
- semantic patches
- source directories
Regards,
Markus
next prev parent reply other threads:[~2014-04-11 6:15 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-04-10 17:48 [PATCH] coccinelle: add pycocci wrapper for multithreaded support Luis R. Rodriguez
2014-04-10 17:48 ` [Cocci] " Luis R. Rodriguez
2014-04-10 17:51 ` Johannes Berg
2014-04-10 17:51 ` [Cocci] " Johannes Berg
2014-04-10 17:57 ` Luis R. Rodriguez
2014-04-10 17:57 ` [Cocci] " Luis R. Rodriguez
2014-04-10 19:32 ` Julia Lawall
2014-04-10 19:32 ` Julia Lawall
2014-04-11 8:50 ` [Cocci] Software parallelisation? SF Markus Elfring
2014-04-11 18:49 ` Jesper Louis Andersen
2014-04-11 19:40 ` SF Markus Elfring
2014-04-11 20:04 ` Julia Lawall
2014-04-11 20:42 ` [Cocci] Adjustments for Coccinelle's software build process? SF Markus Elfring
2014-04-11 20:55 ` [Cocci] Software parallelisation? SF Markus Elfring
2014-08-28 3:46 ` [Cocci] [PATCH] coccinelle: add pycocci wrapper for multithreaded support Luis R. Rodriguez
2014-08-28 3:46 ` Luis R. Rodriguez
2014-08-28 18:15 ` Julia Lawall
2014-08-28 18:15 ` Julia Lawall
2014-08-28 20:02 ` Luis R. Rodriguez
2014-08-28 20:02 ` Luis R. Rodriguez
2014-04-11 5:55 ` SF Markus Elfring
2014-04-11 5:55 ` [Cocci] " SF Markus Elfring
2014-04-11 6:01 ` Julia Lawall
2014-04-11 6:01 ` Julia Lawall
2014-04-11 6:15 ` SF Markus Elfring [this message]
2014-04-11 6:15 ` SF Markus Elfring
2014-04-11 19:00 ` Luis R. Rodriguez
2014-04-11 19:00 ` Luis R. Rodriguez
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=5347886F.8070307@users.sourceforge.net \
--to=elfring@users.sourceforge.net \
--cc=backports@vger.kernel.org \
--cc=cocci@systeme.lip6.fr \
--cc=johannes@sipsolutions.net \
--cc=julia.lawall@lip6.fr \
--cc=linux-kernel@vger.kernel.org \
--cc=mcgrof@suse.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 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.