Re: [Gems-users] (no subject)

["Mike Marty" <mike.marty@xxxxxxxxx>]

Setting that parameter to 1, with protocols that use "recycle", could
lead to starvation.  The in_port processing occurs in the same order
that they appear in the controller specification file.

On Thu, Jun 5, 2008 at 7:27 PM, Chandru Velayutham
<velayucu@xxxxxxxxxxxx> wrote:
> Hi all,
>
> I have a quick question about L2_CACHE_TRANSITIONS_PER_RUBY_CYCLE parameter.
> I think it limits the maximum number of transitions a  L2 cache state controller could process
> Per ruby cycle.
>
> Is there any minimum limit on the value taken by the parameter.
> i.e If I would like to have one transition per ruby cycle,
> can I set L2_CACHE_TRANSITIONS_PER_RUBY_CYCLE : 1 ?
>
> If someone could clarify this, it shall be helpful.
>
> Thanks
> Chandru V
> Computer Engg Graduate Student
> University of Cincinnati
> Ph: (513)-295-8308
> _______________________________________________
> 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.
>
>