On Thu, Aug 28, 2014 at 08:15:16PM +0200, Julia Lawall wrote:
>
>
> On Thu, 28 Aug 2014, Luis R. Rodriguez wrote:
>
> > On Thu, Apr 10, 2014 at 09:32:34PM +0200, Julia Lawall wrote:
> > >
> > >
> > > On Thu, 10 Apr 2014, Luis R. Rodriguez wrote:
> > >
> > > > On Thu, Apr 10, 2014 at 07:51:29P
On Thu, 28 Aug 2014, Luis R. Rodriguez wrote:
> On Thu, Apr 10, 2014 at 09:32:34PM +0200, Julia Lawall wrote:
> >
> >
> > On Thu, 10 Apr 2014, Luis R. Rodriguez wrote:
> >
> > > On Thu, Apr 10, 2014 at 07:51:29PM +0200, Johannes Berg wrote:
> > > > On Thu, 2014-04-10 at 10:48 -0700, Luis R. R
On Thu, Apr 10, 2014 at 09:32:34PM +0200, Julia Lawall wrote:
>
>
> On Thu, 10 Apr 2014, Luis R. Rodriguez wrote:
>
> > On Thu, Apr 10, 2014 at 07:51:29PM +0200, Johannes Berg wrote:
> > > On Thu, 2014-04-10 at 10:48 -0700, Luis R. Rodriguez wrote:
> > >
> > > > You just pass it a cocci file, a
On Fri, Apr 11, 2014 at 08:01:04AM +0200, Julia Lawall wrote:
>
>
> On Fri, 11 Apr 2014, SF Markus Elfring wrote:
>
> > > I checked the profile results, the reason the jobs finish is some threads
> > > had no work or little work.
> >
> > Could you find out during the data processing which parts
>> 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 h
On Fri, 11 Apr 2014, SF Markus Elfring wrote:
> > I checked the profile results, the reason the jobs finish is some threads
> > had no work or little work.
>
> Could you find out during the data processing which parts or files
> result in a special application behaviour you would like to point
> I checked the profile results, the reason the jobs finish is some threads
> had no work or little work.
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?
Regards,
Markus
--
To unsubscribe from this list
On Thu, 10 Apr 2014, Luis R. Rodriguez wrote:
> On Thu, Apr 10, 2014 at 07:51:29PM +0200, Johannes Berg wrote:
> > On Thu, 2014-04-10 at 10:48 -0700, Luis R. Rodriguez wrote:
> >
> > > You just pass it a cocci file, a target dir, and in git environments
> > > you always want --in-place enabled.
On Thu, Apr 10, 2014 at 07:51:29PM +0200, Johannes Berg wrote:
> On Thu, 2014-04-10 at 10:48 -0700, Luis R. Rodriguez wrote:
>
> > You just pass it a cocci file, a target dir, and in git environments
> > you always want --in-place enabled. Experiments and profiling random
> > cocci files with the
On Thu, 2014-04-10 at 10:48 -0700, Luis R. Rodriguez wrote:
> You just pass it a cocci file, a target dir, and in git environments
> you always want --in-place enabled. Experiments and profiling random
> cocci files with the Linux kernel show that using just using number of
> CPUs doesn't scale we
From: "Luis R. Rodriguez"
This is a wrapper for folks which by work on git trees, specifically
the linux kernel with lots of files and with random task Cocci files.
The assumption all you need is multithreaded support and currently only
a shell script is lying around, but that isn't easily extens
11 matches
Mail list logo
