From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mail-pj1-f47.google.com (mail-pj1-f47.google.com [209.85.216.47]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by smtp.subspace.kernel.org (Postfix) with ESMTPS id 27A89312839 for ; Mon, 20 Oct 2025 13:49:21 +0000 (UTC) Authentication-Results: smtp.subspace.kernel.org; arc=none smtp.client-ip=209.85.216.47 ARC-Seal:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1760968163; cv=none; b=T9uNrYxgsq116v5NFwD8v77WE6de+orMElkNSoU6tWs/WvHiJxgSMlOXpmjelDrnZwEU9/J1bicLP9LbXWoENP0DVppIJsj1pFreHN2LPFpitXHMg3mswqyeGZ0bfvShtYjFKLOI4wG7MQpzBqG84NdYaLmVQ9+nAMpPm68CsXs= ARC-Message-Signature:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1760968163; c=relaxed/simple; bh=h3HoLkT4aFAk87mxUyKqKSEwXQ3salm8bUf/3v+FYOg=; h=From:To:Cc:Subject:Date:Message-ID:MIME-Version; b=HgMqx2UbfnDjKcXpZ8tP0K6A+6kEN9Gq3uzwSiJDeMi4RNTNKKfZFPb5JqlD7NxBqd+gE8IIvIpm79+CNZ7cdyxPf/A13a1Wfp+7C5up5Y3EUJQkse+4mtN31Zave8qoQuxm72n6Z5xijX9Jd14BEvJB/IcjVtjW9x7tUJwTSwU= ARC-Authentication-Results:i=1; smtp.subspace.kernel.org; dmarc=pass (p=none dis=none) header.from=gmail.com; spf=pass smtp.mailfrom=gmail.com; dkim=pass (2048-bit key) header.d=gmail.com header.i=@gmail.com header.b=RXyAzkLs; arc=none smtp.client-ip=209.85.216.47 Authentication-Results: smtp.subspace.kernel.org; dmarc=pass (p=none dis=none) header.from=gmail.com Authentication-Results: smtp.subspace.kernel.org; spf=pass smtp.mailfrom=gmail.com Authentication-Results: smtp.subspace.kernel.org; dkim=pass (2048-bit key) header.d=gmail.com header.i=@gmail.com header.b="RXyAzkLs" Received: by mail-pj1-f47.google.com with SMTP id 98e67ed59e1d1-33bb1701ca5so3594250a91.3 for ; Mon, 20 Oct 2025 06:49:21 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20230601; t=1760968161; x=1761572961; darn=vger.kernel.org; h=content-transfer-encoding:mime-version:message-id:date:subject:cc :to:from:from:to:cc:subject:date:message-id:reply-to; bh=mWKmwdA9I2ITUhToX2qR1cuSgLsOWMNN48NL48WMTnk=; b=RXyAzkLsG1wE1CXF+A/i/bMMNnpWQFaePQTpR7AaRTGnluDhvV/Sbn9qgZ31KB0Ir0 p5SkyM1HWWrw267VPbpC7DlLu8A/WZgDKSaB0CG7BCZ/JIVRkQeKgWvnGX4EbFHpSBy+ 3ArsvbcZqQDjZb8B1UNjn3q4U7XpYwbiUtt1aW3JMancQCJU/K5w6PC4kLLcqOgu3tZ7 OuzEra4u22j8XEhdBptFiGHbxMmMHELF6Q56FSW9T8A9Sc3RPzQn2CFRImOePZWtxmG0 E3ULX2CoGyX2Yzb7TRFB5gaIWW08vnNwUqs5IVJy0QM76OX0syJh21cEVU2kCvIuj2HE OSEQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1760968161; x=1761572961; h=content-transfer-encoding:mime-version:message-id:date:subject:cc :to:from:x-gm-message-state:from:to:cc:subject:date:message-id :reply-to; bh=mWKmwdA9I2ITUhToX2qR1cuSgLsOWMNN48NL48WMTnk=; b=evWoX1C+wpJ7tXvhopiWWQfBNeJ80rLg9mUNNwlBwov1UIbhtrH8QPwBygcvlLV8hx VaZQhY5RtXxh5FK1fBgzgK963oAL3OFQJl5I5rv4BamWvubjOW+uQriHgMvmePlNTkro oQ8RDsZvdeiUHxv9OA2zh+Q0sewLVIJ2eriXxUWyZrYLj72D42fJHPBxWqHlST/mi+M4 S5UzyY1qeuzdg1HQLijAXcWzJnjNS4p+dPAivHTn1fdhW83s68kFURAMnk6Mr52qPMXu i5bFAlTKzx0I/V8+LjDMcqK+1YFrkV9GjJjld6LGujbcl2vVQVQVmVZIexm6nP4U/mdI 0wow== X-Forwarded-Encrypted: i=1; AJvYcCXebnwIvzAAfcfK2WMYPi59cnshMeW34ELFWv4Br24CV8akrqMa98obQXKEjXkHK8gMheq4Ibn4n+tdaiU=@vger.kernel.org X-Gm-Message-State: AOJu0YyBxLuDEBkadYOHJhMOLyYKzzkfXj+zxX4u/e1DpSxfN+9RK1Ns sYier7/9n0k7MoKN9BXE8GUWe8rvEQA5kN+kwtdJ2qC/63bUUlT32fHk X-Gm-Gg: ASbGnctfvASoVFaau1WvQgMgbIsSUo7UhW/KtKVaPvkVUrwh+oa0EFSQlHbD85QlKCU uO1VvnYqyDYNM2i6/9XA8ZVOteenZluGcgLHPnmObPqOWC730wWx2ZAQkPLPWzX0AOECeB8Rbsg EkKU3KKXoFJEKlrprZlWMwrtfgrpv9Y+aSG+8vM6DaatDYGvNP93NbC6CuNDUPvHtcg607xMStW cveEtTgSF9SIG5mBThgpZnafEeUyuws8EISEodA/LxKGYDQ+B/i8pbjpzYpddneafxmiJgdZw2G ritzgGXF4zrRa9BP9OJJBLynP4TRAZrAzyAc5KXJCU4yzM/nlFAcwCqtRwjaqrefHt4b/9XAWq+ AKI95WHTLZ65wbYVBadMnnqMzcArpUlUsXC+VQdYwaBScoKwOqkoDVSmHv5fNspF0/FDmeWFizx bDrJK90gps2cwpQmTWnxCsk6ETyh3faLU6NyoUccVcyNU4rAO3bGgONjL7Z3NsKQI3OfkrVI2oy RVnxeSflYaY X-Google-Smtp-Source: AGHT+IESKh8p2QsR+Rk1v/wlAyJsWQauYznHQNj/lfmr1UJMevw6KGFtM4HMsy0OkeBrWdiwqrKe8w== X-Received: by 2002:a17:90a:c2c3:b0:327:f216:4360 with SMTP id 98e67ed59e1d1-33bcf853706mr18348648a91.8.1760968161239; Mon, 20 Oct 2025 06:49:21 -0700 (PDT) Received: from localhost.localdomain ([2401:4900:1cc9:d444:c07a:121f:22da:3f7b]) by smtp.gmail.com with ESMTPSA id 98e67ed59e1d1-33bdd02793dsm4507349a91.3.2025.10.20.06.49.15 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Mon, 20 Oct 2025 06:49:20 -0700 (PDT) From: I Viswanath To: davem@davemloft.net, edumazet@google.com, kuba@kernel.org, pabeni@redhat.com, horms@kernel.org, sdf@fomichev.me, kuniyu@google.com, ahmed.zaki@intel.com, aleksander.lobakin@intel.com, andrew+netdev@lunn.ch Cc: netdev@vger.kernel.org, linux-kernel@vger.kernel.org, skhan@linuxfoundation.org, linux-kernel-mentees@lists.linux.dev, david.hunter.linux@gmail.com, khalid@kernel.org, I Viswanath Subject: [RFC net-next PATCH 0/2] net: Split ndo_set_rx_mode into snapshot and deferred write Date: Mon, 20 Oct 2025 19:18:55 +0530 Message-ID: <20251020134857.5820-1-viswanathiyyappan@gmail.com> X-Mailer: git-send-email 2.47.3 Precedence: bulk X-Mailing-List: linux-kernel@vger.kernel.org List-Id: List-Subscribe: List-Unsubscribe: MIME-Version: 1.0 Content-Transfer-Encoding: 8bit This is an implementation of the idea provided by Jakub here https://lore.kernel.org/netdev/20250923163727.5e97abdb@kernel.org/ ndo_set_rx_mode is problematic because it cannot sleep. To address this, this series proposes dividing existing set_rx_mode implementations into set_rx_mode and write_rx_config The new set_rx_mode will be responsible for updating the rx_config snapshot which will be used by ndo_write_rx_config to update the hardware In brief, The callback implementations should look something like: set_rx_mode(): prepare_rx_config(); update_snapshot(); write_rx_mode(): read_snapshot(); do_io(); write_rx_mode() is called from a work item making it sleepable during the do_io() section. This model should work correctly if the following conditions hold: 1. write_rx_config should use the rx_config set by the most recent call to set_rx_mode before its execution. 2. If a set_rx_mode call happens during execution of write_rx_config, write_rx_config should be rescheduled. 3. All calls to modify rx_mode should pass through the set_rx_mode + schedule write_rx_config execution flow. 1 and 2 are guaranteed because of the properties of work queues Drivers need to ensure 3 ndo_write_rx_config has been implemented for 8139cp driver as proof of concept To use this model, a driver needs to implement the ndo_write_rx_config callback, have a member rx_config in the priv struct and replace all calls to set rx mode with schedule_and_set_rx_mode(); I Viswanath (2): net: Add ndo_write_rx_config and helper structs and functions: net: ethernet: Implement ndo_write_rx_config callback for the 8139cp driver drivers/net/ethernet/realtek/8139cp.c | 67 ++++++++++++++++++--------- include/linux/netdevice.h | 38 ++++++++++++++- net/core/dev.c | 48 +++++++++++++++++-- 3 files changed, 127 insertions(+), 26 deletions(-) --- I tested the correctness of this by comparing rx_config request in set_rx_config and written values in write_rx_config. The prints I used: After new_config is set in set_rx_mode: printk("Requested Values: rx_config: %8x, mc_filter[0]: %8x, mc_filter[1]: %8x", new_config.rx_mode, new_config.mc_filter[0], new_config.mc_filter[1]); After the writes in write_rx_config: printk("RxConfig: %8x", cpr32(RxConfig)); printk("MC Filter[0]: %8x, MC Filter[1]: %8x", cpr32(MAR0 + 0), cpr32(MAR0 + 4)); Is this sufficient testing for a proof of concept? I picked 8139cp because I could emulate it on QEMU and it was somewhat easy to refactor. -- 2.47.3