Re: [Gems-users] GARNET: Bandwidth


Date: Tue, 28 Apr 2009 16:17:23 -0400
From: "Niket Agarwal (niketa@xxxxxxxxxxxxx)" <niketa@xxxxxxxxxxxxx>
Subject: Re: [Gems-users] GARNET: Bandwidth
hmm .. could you send me your network config file, your ruby config file and the NetworkLink_d file . I will be in a better position to comment after taking a look at them. 

Cheers, 
Niket

----- Original Message -----
From: kanchan damle <kanchan.damle@xxxxxxxxx>
Date: Tuesday, April 28, 2009 12:35 pm
Subject: Re: [Gems-users] GARNET: Bandwidth
To: Gems Users <gems-users@xxxxxxxxxxx>

> Niket,
> 
> I did what you said, I am getting deadlocks and the simulation is 
> crashing,
> So what I am doing in the wakeup function is ,
> 
> Checking for linkBuffer->isEmpty
> --  if true then go ahead and pull the flit out of link-srcqueue 
> and insert
> in Link buffer
> 
> --   if false then getTopFlit from linkBuffer and then flit-
> >get_time() and
> compare it with the current time.
>     If the timestamp on the flit is less than or equal to current 
> time,then I allow the new flit to be inserted.
> 
> Am I missing out on something?
> 
> Thanks a lot in advance.
> 
> On Mon, Apr 27, 2009 at 10:13 PM, kanchan damle 
> <kanchan.damle@xxxxxxxxx>wrote:
> > Thanks a lot Niket!
> >
> >
> > On Mon, Apr 27, 2009 at 3:34 PM, Niket Agarwal 
> <niketa@xxxxxxxxxxxxx>wrote:>
> >> Per-link bandwidth can be changed by changing the latency of the 
> link>> whose bandwidth is to be changed. For e.g., if you want a 
> link with
> >> half the bandwidth, you should increase the latency to two cycles
> >> assuming all other links are one cycle. Now, one thing is to be 
> added>> to NetworkLink_d.C; If nothing is added, every flit will 
> take two
> >> cycles but flits will travel in a pipelined manner. So, the 
> bandwidth>> is not reduced. What needs to be done is: in the wakeup 
> function, a
> >> flit should be picked up from the source queue only if either the
> >> following is true:
> >>
> >> 1. The linkBuffer is empty
> >> 2. The flit in linkBuffer is about to be picked up by Input of 
> Router>> this cycle. This can be checked by comparing the current 
> time with the
> >> timestamp in the flit present at linkBuffer.
> >>
> >> Adding these should solve your problem.
> >>
> >> Cheers,
> >> Niket
> >>
> >> ----- Original Message -----
> >> From: kanchan damle <kanchan.damle@xxxxxxxxx>
> >> Date: Monday, April 27, 2009 2:53 pm
> >> Subject: [Gems-users] GARNET: Bandwidth
> >> To: Gems Users <gems-users@xxxxxxxxxxx>
> >>
> >> > Dear Gems Users,
> >> >
> >> > I was working on a fat tree topology and wanted to vary the
> >> > bandwidth to
> >> > account for congestion control for upper levels of the tree.
> >> > I do understand that in Garnet, bandwidth = flit size.
> >> >
> >> > I was wondering, whether it is feasible to vary the link width 
> and how
> >> > complex would that be?
> >> >
> >> > Thanks a lot in advance.
> >> >
> >> > ---
> >> > Kanchan
> >> >
> >> _______________________________________________
> >> 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.
> >>
> >>
> >
> 
[← Prev in Thread] Current Thread [Next in Thread→]