netdev - Re: [Question] What's the noop_qdisc introduced for in the kernel?

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:	Tue, 30 Dec 2014 12:15:01 -0800
From:	Cong Wang <cwang@...pensource.com>
To:	Dennis Chen <kernel.org.gnu@...il.com>
Cc:	netdev <netdev@...r.kernel.org>
Subject: Re: [Question] What's the noop_qdisc introduced for in the kernel?

On Tue, Dec 30, 2014 at 1:23 AM, Dennis Chen <kernel.org.gnu@...il.com> wrote:
> After google and the code reading, seems this Qdisc instance is only
> used for the initialization purpose, I can't find the reason that this
> object introduced in the kernel. Does anybody know what the historical
> reason is for this invention? the purpose or the benefit for this
> Qdisc object?
>

Not just for initialization, it is kinda a null qdisc when
the previous qdisc gets removed:

        /* ... and graft new one */
        if (qdisc == NULL)
                qdisc = &noop_qdisc;

or the entire device is not activated yet. It guarantees no
packets can be sent out via this qdisc.
--
To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html