Yes; a simple change the the workload definition will create threads
vs processes.
The clause:
define process, instances=n
{
thread , instances=n
{
...
}
}
You can arrange the process/thread relationship anyway you like. In
the simplest case to make something multiprocess, change the process instances
in the workload definition to be more than one, and leave the
instances in the thread definition to one; i.e. create one thread per process.
Regards,
Richard.
On Mon, Nov 14, 2005 at 07:38:10AM -0800, Timothy Butler wrote:
> I've extended filebench to write through a device specific API, and so far
> my rudimentary support works ok. But I've found a platform specific difference
> that raises a usage question of threads versus processes.
>
> If USE_PROCESS_MODEL is defined, procflow_createproc() will fork/exec a
> process,
> otherwise it will spawn a thread. Is there a way to control the usage of
> threads
> vs. processes in the workload description? (on a platform that will support
> both,
> of course) I'd like to be able to measure behavior both ways.
>
> I ran into this issue when I found the code I'd added worked on a linux 2.4
> system,
> but not on a Solaris 10 system, where I'd rather develop. I had added to the
> grammar to parse parameters my code needs, which I then put into the flowop
> structure. But after the fork/exec, the child process of course does not have
> a
> copy of the flowop structure from the parent, and the parameters are
> unavailable.
>
> Does that structure get put into shared memory so all spawned processes can
> access
> it? (It looks like it does, at least sometimes, in flowop_define_common)
>
> thanks,
> tim
> This message posted from opensolaris.org
> _______________________________________________
> perf-discuss mailing list
> perf-discuss@opensolaris.org
--
:-:-:-:-:-:-:-:-:-:-:-:-:-:-:-:-:-:-:-:-:-:-:-:-:-:-:-:-:-:-:-:-:-:-:-:
Richard Mc Dougall : [EMAIL PROTECTED]
Performance and Availability : x31542
Engineering : http://blogs.sun.com/rmc
Sun Microsystems Inc : +1 650 352 6438
:-:-:-:-:-:-:-:-:-:-:-:-:-:-:-:-:-:-:-:-:-:-:-:-:-:-:-:-:-:-:-:-:-:-:-:
_______________________________________________
perf-discuss mailing list
perf-discuss@opensolaris.org
