quoted

From 71843907bdb9cdc4e24358f0c16a8778f2762dc7 Mon Sep 17 00:00:00 2001
From: Niclas Hedam <redacted>
Date: Fri, 25 Jun 2021 13:37:18 +0200
Subject: [PATCH] net: sched: Add support for packet bursting.

Something went wrong with the formatting here.

I'll resubmit with fixed formatting. My bad.

quoted

This commit implements packet bursting in the NetEm scheduler.
This allows system administrators to hold back outgoing
packets and release them at a multiple of a time quantum.
This feature can be used to prevent timing attacks caused
by network latency.

How is this bursting feature different from the existing slot-based
mechanism?

It is similar, but the reason for separating it is the audience that they are catering.
The slots seems to be focused on networking constraints and duty cycles.
My contribution and mechanism is mitigating timing attacks. The complexity of slots are mostly unwanted in this context as we want as few CPU cycles as possible.

On 28 Jun 2021, at 13:44, Toke Høiland-Jørgensen [off-list ref] wrote:

Niclas Hedam [off-list ref] writes:

quoted

From 71843907bdb9cdc4e24358f0c16a8778f2762dc7 Mon Sep 17 00:00:00 2001
From: Niclas Hedam <redacted>
Date: Fri, 25 Jun 2021 13:37:18 +0200
Subject: [PATCH] net: sched: Add support for packet bursting.

Something went wrong with the formatting here.

quoted

This commit implements packet bursting in the NetEm scheduler.
This allows system administrators to hold back outgoing
packets and release them at a multiple of a time quantum.
This feature can be used to prevent timing attacks caused
by network latency.

How is this bursting feature different from the existing slot-based
mechanism?

-Toke