Re: [OPENETLAB] Question: Oplets and Accelar Queue Mgt./Routing

["Vivek Sawant" <vivek@nortelnetworks.com>]

Muneyb Minhazuddin wrote:
> 
> > Hi All,
> >
> > I am playing with an idea of influencing Accelar Forwarding from Oplets.
> > I am looking at an algorithm which is an extension to RED. I wonder if I
> > can implement it as an Oplet and combine it with Accelar IPfilter
> > setting to influence Accelar Packet forwarding.
> >
> > My initial investigation suggests that this is not possible. Here is
> > why. This algorithm, like any other queue management algorithm, includes
> > the just arrived packet in a computation to decide if the packet should
> > be dropped or queued. If this computation happens in an Oplet, it is
> > essentially happening outside the Accelar forwarding path. Given current
> > Accelar filter actions, one can either choose to drop or forward a
> > packet (besides getting a copy of it, etc.) One cannot pull a packet
> > out, do computations and then give it back to Accelar forwarding engine.
> 
> > (I know, it will radically slow the engine down.) So, such a queue
> > management algo has to be part of the Accelar forwarding mechanism.
> 
> That is right.
> 
> > Is my inference correct or is it still possible to implement such a
> > scheme through Oplets?
> 
> My understanding is that Oplets provide services. If you have any specific
> forwarding rules that you want to write using an oplet into the forwarding
> path you would make use of JFWD.

Well, that's probably what I meant.

> 
> RED implementation would have to be hardcoded, however ability to pass
> parameters like max threshold, min threshold, burst, probability of drop
> using a mapping from JFWD is probably prefered.

That's fine. I am trying to see if one can use ORE/JFWD set up as an
experimental platform for trying out new queue management strategies.
I don't mind if the RED is absent or not activated in Accelar.
If I can send packets to Accelar (output ports), I would be happy.

_vivek