Just as Mike said, did your requestNetwork_out's and requestQueue_in's corresponding MessageBuffer has the same virtual_network number? In fact, a MessageBuffer can only receive messages come from the same virtual_network.
2007/3/28, Dave Z. <zhu_dave@xxxxxxxxx>:
Everything works fine if I enqueue the message to unblockNetwork_out. Any ideas why it doesn't work with
requestNetwork_out?
Thanks,
D.
--- "Dave Z." <zhu_dave@xxxxxxxxx> wrote:
> Hi Hongxia, > > Thanks for your reply! I defined a function in
> RubySlicc_ComponentMapping. The function takes L1 > machineID as argument and returns the local > directory > machineID. After I enqueue the message to > requestNetwork_out, the directory controller does
> not > receive it in its requestQueue_in. Is there anything > I'm missing? > > Thanks. > > D. > > --- hongxia sun <sunhx.seraph@xxxxxxxxx
> wrote: > > > Hi Dave, > > > > Where did you set the destination id? You'd better > > set it in *.sm files and > > set it as other similar action does. Because ruby
> > need to change the > > machineID into their corresponding nodeID in the > > network. > > > > Hope it can be help. > > > > Good luck! > > > > Hongxia SUN
> > > > > > 2007/3/27, Dave Z. <zhu_dave@xxxxxxxxx>: > > > > > > Hello, > > > > > > I've been unsuccessful with sending a message
> from > > the > > > cache controller (id:1) to the directory > > controller > > > (id:1) via request queue. When I enqueue a > message > > to > > > requestNetwork_out, I set the destination to
> > machineID > > > (which gives errors) or I set the destination to > a > > > global variable same as the id of the cache > > controller > > > (which does not send the message to
> > requestQueue_in. > > > Is there anything that might prevent message > > transfers > > > between cache controllers and directory > > controllers of > > > the same id?
> > > > > > Thanks, > > > > > > Dave > > > > > > > > > > > > > > > > > > ____________________________________________________________________________________
> > > Never miss an email again! > > > Yahoo! Toolbar alerts you the instant new Mail > > arrives. > > > > > >
http://tools.search.yahoo.com/toolbar/features/mail/ > > > _______________________________________________ > > > Gems-users mailing list > > >
Gems-users@xxxxxxxxxxx > > > > > > https://lists.cs.wisc.edu/mailman/listinfo/gems-users > > > Use Google to search the GEMS Users mailing list
> > by adding "site: > > > https://lists.cs.wisc.edu/archive/gems-users/" > to > > your search. > > >
> > > > > > _______________________________________________ > > Gems-users mailing list > > Gems-users@xxxxxxxxxxx > > >
https://lists.cs.wisc.edu/mailman/listinfo/gems-users > > Use Google to search the GEMS Users mailing list > by > > adding > >
> "site:https://lists.cs.wisc.edu/archive/gems-users/" > > to your search. > > > > > > > >
> ____________________________________________________________________________________ > Never miss an email again! > Yahoo! Toolbar alerts you the instant new Mail > arrives. >
http://tools.search.yahoo.com/toolbar/features/mail/ > _______________________________________________ > Gems-users mailing list > Gems-users@xxxxxxxxxxx
> https://lists.cs.wisc.edu/mailman/listinfo/gems-users > Use Google to search the GEMS Users mailing list by > adding > "site:
https://lists.cs.wisc.edu/archive/gems-users/" > to your search. > >
____________________________________________________________________________________
Bored stiff? Loosen up... Download and play hundreds of games for free on Yahoo! Games. http://games.yahoo.com/games/front _______________________________________________
Gems-users mailing list Gems-users@xxxxxxxxxxx https://lists.cs.wisc.edu/mailman/listinfo/gems-users
Use Google to search the GEMS Users mailing list by adding "site:https://lists.cs.wisc.edu/archive/gems-users/" to your search.
|