On Wed, 22 Jun 2016 12:03:55 +0200
Florian Westphal wrote:
> Currently classification and enqueue is done in a single step.
>
> core acquires the qdisc lock, then calls the ->enqueue() function
> of the qdisc.
>
> Its the job of the qdisc and its attached classifiers to figure out what
> to do
Alexei Starovoitov wrote:
> On Wed, Jun 22, 2016 at 3:03 AM, Florian Westphal wrote:
> > Currently classification and enqueue is done in a single step.
> >
> > core acquires the qdisc lock, then calls the ->enqueue() function
> > of the qdisc.
> >
> > Its the job of the qdisc and its attached cla
On Wed, Jun 22, 2016 at 3:03 AM, Florian Westphal wrote:
> Currently classification and enqueue is done in a single step.
>
> core acquires the qdisc lock, then calls the ->enqueue() function
> of the qdisc.
>
> Its the job of the qdisc and its attached classifiers to figure out what
> to do next.
Cong Wang wrote:
> On Wed, Jun 22, 2016 at 3:03 AM, Florian Westphal wrote:
> >
> > This (unfinished!) hack splits classification and enqueue into
> > two steps.
> >
> > Before enqueueing the packet and *before* acquiring the root qdisc lock,
> > the new qdisc ->classify() function is invoked.
>
On Wed, Jun 22, 2016 at 3:03 AM, Florian Westphal wrote:
>
> This (unfinished!) hack splits classification and enqueue into
> two steps.
>
> Before enqueueing the packet and *before* acquiring the root qdisc lock,
> the new qdisc ->classify() function is invoked.
>
> This function -- much like enq
Currently classification and enqueue is done in a single step.
core acquires the qdisc lock, then calls the ->enqueue() function
of the qdisc.
Its the job of the qdisc and its attached classifiers to figure out what
to do next.
Typically the enqueue function will call tc_classify() to lookup a
c
