linux-kernel - net-sched: When TX over-limit happens on netdev, what does kernel do?

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-next>] [day] [month] [year] [list]

Message-ID: <CAFgQCTtg1U7V_WbJ2uZG9unM5qV6sPfoCMbrMVdXrebwue6wzg@mail.gmail.com>
Date:	Sun, 1 Apr 2012 16:27:32 +0800
From:	Liu ping fan <kernelfans@...il.com>
To:	linux-net@...r.kernel.org
Cc:	Jamal Hadi Salim <hadi@...erus.ca>, linux-kernel@...r.kernel.org
Subject: net-sched: When TX over-limit happens on netdev, what does kernel do?

Hi,

Could anybody tell me when TX over-limit happens on netdev, what does kernel do?
Is skb buffered in Qdisc->q and the sending process keeps running?
Or we block the sending process and make it scheduled?

Found some code in net/sched/sch_cbq.c
cbq_dequeue(struct Qdisc *sch) --> qdisc_watchdog_schedule(),  so I
guess the skb is buffered in Qdisc, but what about sending process?

Thanks and regards,
pingfan
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/