Anyone know what "enqueque" means?

[rrruss]

A student asked my wife what "enqueque" means and I cannot find anything making much sense on Google!

It's something to do with downloading music, possibly using WinAmp. Personally I think the word is really "enqueue" but am hoping some of you techno experts will know best.

Thanks

Russ

 

[Badger]

I think they mean "enqueue" which is probably just adding music to your download list

 

[gullshark]

putting stuff in a queue

 

[Titanic]

From my IBM mainframe days, an ENQueue is the means by which an executing program requests control of a serially reusable resource.

You issue an ENQ in your program and specifies the name(s) of the resource(s) and if you want shared (typically read access) or exclusive control (typically for update access). If the resource is not available, your task is suspended on a wait queue until the resource becomes available. Once you have finished using the resource you use the DEQueue macro to release it.

But I'm guessing that is not what your wife's student was asking about.

 

[Cian]

It adds files to the playlist, its "Enqueue".

 

[REDLAND]

Its a reserved word in The Python script language thats often used for writing multi media apps (like WinAmp)

when applied it means:- don't clear the playlist

 

[Monkster]

It adds files to the playlist, its "Enqueue".

That's the first time I've EVER understood a tech explanation from you

Keep it going

 

[TonyW]

Here you go, piece of piss

Enqueue
The enqueue function enqueues a packet with the queueing discipline. Packets are enqueued in the following manner. As already shown in the previous section, when the IP layer calls dev_queue_xmit, the enqueue function of the queuing discipline attached to the device is called. This portion of the code in net/core/dev.c is shown below:

q = dev->qdisc;
if (q->enqueue) {
q->enqueue(skb, q);
qdisc_wakeup(dev);
return 0;
}

In the enqueue function of a queuing discipline, the filters are run one by one until a match occurs. Once the match occurs, the enqueue function of the queueing discipline "owned" by that class is executed. For example, in the cbq_enqueue function (in net/sched/sch_cbq.c),

struct cbq_class *cl = cbq_classify(skb, sch);
int len = skb->len;

if (cl && cl->q->enqueue(skb, cl->q) == 1)
.
.

The function cbq_classify is used to apply the filters and determine the class to which to the packet belongs. After that, the enqueue function of the queuing discipline owned by that class is called. This queuing discipline may have its own classes, which in turn may be associated with some other queuing discipline, and so on, which makes the usage flexible, as was discussed earlier.

At this point, it is worth mentioning that when a class is created, the default queuing discipline that it owns is a Priority FIFO queue. The portion of the code (in net/sched/sch_cbq.c) that does this is shown below.

static int cbq_init(struct Qdisc *sch, struct rtattr *opt)
{
.
.
.

if (!(q->link.q = qdisc_create_dflt(sch->dev, &pfifo_qdisc_ops)))
q->link.q = &noop_qdisc;
.
.
.
}

This can be changed by doing a graft operation, that will be discussed later in the section on classes.

 

[rrruss]

So, I was right then. She really meant "enqueue". That's a big fat zero on her spelling exam then!!

 

[Lord Bracknell]

Originally Posted by Monkster

It adds files to the playlist, its "Enqueue".

That's the first time I've EVER understood a tech explanation from you

Keep it going

Here you go, piece of piss

Enqueue
The enqueue function enqueues a packet with the queueing discipline. Packets are enqueued in the following manner. As already shown in the previous section, when the IP layer calls dev_queue_xmit, the enqueue function of the queuing discipline attached to the device is called. This portion of the code in net/core/dev.c is shown below:

q = dev->qdisc;
if (q->enqueue) {
q->enqueue(skb, q);
qdisc_wakeup(dev);
return 0;
}

In the enqueue function of a queuing discipline, the filters are run one by one until a match occurs. Once the match occurs, the enqueue function of the queueing discipline "owned" by that class is executed. For example, in the cbq_enqueue function (in net/sched/sch_cbq.c),

struct cbq_class *cl = cbq_classify(skb, sch);
int len = skb->len;

if (cl && cl->q->enqueue(skb, cl->q) == 1)
.
.

The function cbq_classify is used to apply the filters and determine the class to which to the packet belongs. After that, the enqueue function of the queuing discipline owned by that class is called. This queuing discipline may have its own classes, which in turn may be associated with some other queuing discipline, and so on, which makes the usage flexible, as was discussed earlier.

At this point, it is worth mentioning that when a class is created, the default queuing discipline that it owns is a Priority FIFO queue. The portion of the code (in net/sched/sch_cbq.c) that does this is shown below.

static int cbq_init(struct Qdisc *sch, struct rtattr *opt)
{
.
.
.

if (!(q->link.q = qdisc_create_dflt(sch->dev, &pfifo_qdisc_ops)))
q->link.q = &noop_qdisc;
.
.
.
}

This can be changed by doing a graft operation, that will be discussed later in the section on classes.

Thank you TonyW. You've rescued MYOB's technical explanation from being understandable.