Always enable bandwidth control in Q
The current bindwith control check the qtaguid module before start. But
since the bandwidth controlling feature is tested by CTS already, all
devices should have either xt_qtaguid or proper eBPF program to support
that by default. So just delete the checking code and always try to turn
it on when device start
Bug: 30950746
Test: The bindwith control start correctly on new devices.
Change-Id: I4cc5ebfbcf89181fcdba3a2711b637722e56ce73
diff --git a/services/core/java/com/android/server/NetworkManagementService.java b/services/core/java/com/android/server/NetworkManagementService.java
index bd0a4c7..cdc1244 100644
--- a/services/core/java/com/android/server/NetworkManagementService.java
+++ b/services/core/java/com/android/server/NetworkManagementService.java
@@ -621,22 +621,17 @@
mBandwidthControlEnabled = false;
- // only enable bandwidth control when support exists
- final boolean hasKernelSupport = new File("/proc/net/xt_qtaguid/ctrl").exists();
-
// push any existing quota or UID rules
synchronized (mQuotaLock) {
- if (hasKernelSupport) {
- Slog.d(TAG, "enabling bandwidth control");
- try {
- mConnector.execute("bandwidth", "enable");
- mBandwidthControlEnabled = true;
- } catch (NativeDaemonConnectorException e) {
- Log.wtf(TAG, "problem enabling bandwidth controls", e);
- }
- } else {
- Slog.i(TAG, "not enabling bandwidth control");
+ // TODO: Delete this code and have netd unconditionally enable bandwidth control at
+ // startup time
+ Slog.d(TAG, "enabling bandwidth control");
+ try {
+ mConnector.execute("bandwidth", "enable");
+ mBandwidthControlEnabled = true;
+ } catch (NativeDaemonConnectorException e) {
+ Log.wtf(TAG, "problem enabling bandwidth controls", e);
}
SystemProperties.set(PROP_QTAGUID_ENABLED, mBandwidthControlEnabled ? "1" : "0");