The communication between GridSim entities is done through sending
a message or event. To know how to response to an incoming event
or what each event wants, each event has a specific tag name.
These tag names are defined in GridSimTags.java (majority of them).
These are the basic principals of GridSim or SimJava.
Example8 shows how you can create a new resource scheduler without
worrying the low-level details, i.e. receiving/sending events.
Thus, a skeleton is provided so that you only concentrate on
implementing these abstract methods to make a new scheduler.
In Example8, the Example8 class sends jobs to a resource.
The resource scheduler is happened to be a NewPolicy object.
Thus, the incoming events, or more specifically, jobs/gridlets
are arriving in the gridletSubmit() function.
Follow the sequence of this example:
http://www.gridbus.org/gridsim/example/Example08/output.txt
anthony
On Sat, 16 Aug 2008, Anish Khanna wrote:
> Hi all,
>
> I came across a class file Example 8 from
> http://www.gridbus.org/gridsim/example/Example08/Example8.java,
>
> While tracing this program using NetBeans IDE, I found that the line
> success = gridletSubmit(gridlet, resourceID[id], 0.0, true);
>
> Takes the program execution to another file NewAllocPolicy.java which is
> another class file in the project.. and calls the gridletSubmit ( ) function
> in there instead of the function in *EXAMPLE8 CLASS* !!!
>
> I am not able to understand if this happens due to interleaving of multiple
> threads..
>
> I am not sure of how articulate I have been in this mail.. But I am sure
> you'd have faced a similar situation had you worked wit Example8..
> I am a tyro to GRIDSIM and NetBeans so excuse me if my doubt is very silly
> :)
>
> Any kinda help regarding this will be appreciated..
> Thanks,
> Anish
>
|
