From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mail-qt1-f178.google.com (mail-qt1-f178.google.com [209.85.160.178]) (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 AC798337BB3 for ; Fri, 6 Mar 2026 23:10:27 +0000 (UTC) Authentication-Results: smtp.subspace.kernel.org; arc=none smtp.client-ip=209.85.160.178 ARC-Seal:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1772838629; cv=none; b=gXwY3B8F1Jp9binEItAdpKphue4xcjQn/sJ+0rsncdX5XmmQ+HzCbPRB1MzQYGXjFMwaqO3XIubrhcmXC05aEyr1X2x5HQqeL/V7i0ctrf2H1x9x2gbLQcYkhglsCKb4YJdF57UADDua6OgwbCQhLqCZEt5cHTWg7H6Jxooipuk= ARC-Message-Signature:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1772838629; c=relaxed/simple; bh=+Wo2K/X+Cq11I5YoP13/K61MVEHaQ70AgPIyYdTnDro=; h=Date:From:To:Cc:Subject:Message-ID:References:MIME-Version: Content-Type:Content-Disposition:In-Reply-To; b=GGXSQe/UPAJhWHF+U/txasAvFL4RC88WMD9OQTtd5EOUGCv2akhXmWzGPSX8+Y8B1Vlb6H/P1zA11C/W/71Gnyx+Iz4VS89buTcO0UzKE6xrqsbGoXB3IT1G5kEKLT37YSBe17c37TtfopVGuiYaqorbMw4JUcw++1tX4VFUCyw= ARC-Authentication-Results:i=1; smtp.subspace.kernel.org; dmarc=none (p=none dis=none) header.from=ziepe.ca; spf=pass smtp.mailfrom=ziepe.ca; dkim=pass (2048-bit key) header.d=ziepe.ca header.i=@ziepe.ca header.b=Wsg+1JCV; arc=none smtp.client-ip=209.85.160.178 Authentication-Results: smtp.subspace.kernel.org; dmarc=none (p=none dis=none) header.from=ziepe.ca Authentication-Results: smtp.subspace.kernel.org; spf=pass smtp.mailfrom=ziepe.ca Authentication-Results: smtp.subspace.kernel.org; dkim=pass (2048-bit key) header.d=ziepe.ca header.i=@ziepe.ca header.b="Wsg+1JCV" Received: by mail-qt1-f178.google.com with SMTP id d75a77b69052e-506a7bbe9d0so69751961cf.0 for ; Fri, 06 Mar 2026 15:10:27 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=ziepe.ca; s=google; t=1772838626; x=1773443426; darn=vger.kernel.org; h=in-reply-to:content-disposition:mime-version:references:message-id :subject:cc:to:from:date:from:to:cc:subject:date:message-id:reply-to; bh=X8xiVcJi/2j0+t3xwC2rYaGHbViIQdp0Z+nSHzUs3cI=; b=Wsg+1JCVrTec4XkcLEFsr9/nUlMWupW7x2g3G1YUHiDimWJ77Yg6+qfbLvAAaUk2SW vkP4fZhatWRyjQ3Fvq+pKs5TALFNAMK4wDFqo3aqiOpGiXINJ7ErRJy+E54PaiMmSomB +WmlTB6RyNlxDd3GPsklgNbgCLdA9wFdb4xAFw0I4hFGhw8EKHUvMH+Pf6Olqj1iKJCq 4OxPR2+3s6SWyTRqPz4x2C4hbqF/8YZ/2JZxNKbQ/NWATHTHPxY0Pt9lk1NP45z3qldq kXOYHO6y0EaFBu0gEsAN1i7cd4x+DAmBLq5R0yicZ3nc8F7e+IXOa+P5bHLm29VUQVfK 2rXw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1772838626; x=1773443426; h=in-reply-to:content-disposition:mime-version:references:message-id :subject:cc:to:from:date:x-gm-gg:x-gm-message-state:from:to:cc :subject:date:message-id:reply-to; bh=X8xiVcJi/2j0+t3xwC2rYaGHbViIQdp0Z+nSHzUs3cI=; b=PaCRLNtY0okUaMjEDo+SJZoZnMOq1oXL3BbohstLtJR2sslX/WxjAzJ3Zn16qubATy gUrDVoK5/1m2Or7znq8/hUtrORGQXaXIVZzCpIAaredmJlWfA98T9bBFnaDa9pY7uQ+V RasVKZg0DPhwEdHwy9yEmCetcZVhIL21Nnrb6/zWS+fCwPwFbF0j99PkhR5vItIB/vQv bQOobvjprhtxtMMl3hW7iSCPLL1A3Yej9a2UDpKQC54cfXtM+90EXyjJZL9bQwVHL1Sn JLdLZESJtfsfOLJwebx9huHqDZkv0exhej9MFCq+Ple5B4krYoCOOwfbw2lvUmnF3aVD Bf4Q== X-Forwarded-Encrypted: i=1; AJvYcCUXEMEO9HF0tvGnSGjTD+0hsxsqkATlajccwSNMcXYQRacV2H6sKQkvBVo2T5ObP4TbTN/QveQ=@vger.kernel.org X-Gm-Message-State: AOJu0YzOw4a2zSy/kQXLzn/CHGci5Q/p2uaRXiRGpOHbEyjI9YdhtbMF IkIRxTd7u4aKMTGenfErKK8DaQmH6VcaDqb3fv3aQDZcIno2Gn/b/GMp2qxGBO7r/78= X-Gm-Gg: ATEYQzwnDattG9zwJCJH1a4i5f1+VC/n6qIa1G4Z/CyHLWSX7WvSA+uTdSjeVtBuR1y sP/vuuEc7YOx+cNI7yhvzbuynqZBS/kyB8cQ8Y2PxDq+pREvURXkCjwrZCz8PCgc9XeEGKrJjCA KxgAg9Cb2U3fJD0vb+iHqEpL7wKkIPBStxPENd5+T/wuc1teLv7dNxnvfSi1+7M8KMf2BKNNUtM O3NzV+Ucn7++OHEg+NnSFAgIyZ5bsJ/D6xU/O6zmmiZNdaswJBYeHmY400x9AjPrDhMIDn8KdZg nUm0/UVx3XCnyIXCdqt/gQDskJl6fXN4g5egkD439ktPCTPU8a379oaz6ftTSiIXbxsbtEnrB1N g9fE127xbZN+dA87Mvv1/ELUj4PS2E5jqoTSVA6InF6usVfDWNXk+IhGdyg++/QX9YXMB2UNIhD aLhW3P69jdCo6OMqG2p54Yh42/UcsI2GyoHpLwd57qIYGFLmzwfQGb3gX7U+0waODIIzIN9hxaN rU3aExl X-Received: by 2002:a05:622a:11c1:b0:506:9b96:6283 with SMTP id d75a77b69052e-508f49980eemr54331101cf.66.1772838626596; Fri, 06 Mar 2026 15:10:26 -0800 (PST) Received: from ziepe.ca (hlfxns017vw-142-162-112-119.dhcp-dynamic.fibreop.ns.bellaliant.net. [142.162.112.119]) by smtp.gmail.com with ESMTPSA id d75a77b69052e-508f66ce03esm18225341cf.27.2026.03.06.15.10.24 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Fri, 06 Mar 2026 15:10:25 -0800 (PST) Received: from jgg by wakko with local (Exim 4.97) (envelope-from ) id 1vyeJM-0000000FcSI-0t9y; Fri, 06 Mar 2026 19:10:24 -0400 Date: Fri, 6 Mar 2026 19:10:24 -0400 From: Jason Gunthorpe To: Praveen Kannoju Cc: "saeedm@nvidia.com" , "leon@kernel.org" , "tariqt@nvidia.com" , "mbloch@nvidia.com" , "andrew+netdev@lunn.ch" , "davem@davemloft.net" , "edumazet@google.com" , "kuba@kernel.org" , "pabeni@redhat.com" , "netdev@vger.kernel.org" , "linux-rdma@vger.kernel.org" , "linux-kernel@vger.kernel.org" , Rama Nichanamatlu , Manjunath Patil , Anand Khoje Subject: Re: [PATCH] net/mlx5: poll mlx5 eq during irq migration Message-ID: <20260306231024.GF1687929@ziepe.ca> References: <20260304161704.910564-1-praveen.kannoju@oracle.com> <20260304201151.GI964116@ziepe.ca> <20260306003217.GB1687929@ziepe.ca> Precedence: bulk X-Mailing-List: netdev@vger.kernel.org List-Id: List-Subscribe: List-Unsubscribe: MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: On Fri, Mar 06, 2026 at 02:19:09PM +0000, Praveen Kannoju wrote: > > > On Thu, Mar 05, 2026 at 05:08:52PM +0000, Praveen Kannoju wrote: > > > > > Regardless of the underlying causes, which may include IRQ loss > > > or EQ re-arming failure, the TX queue becomes stuck, and the > > > timeout handler is only triggered once the queue is declared > > > full. In scenarios where only specialized packets, such as > > > heartbeat packets, are sent through the queue, it takes > > > significantly longer for the queue to fill and be identified as > > > stuck. A proven solution for this issue is polling the EQ > > > immediately after the corresponding IRQ migration, which allows > > > for earlier recovery and prevents the transmission queue from > > > becoming stuck. > > > > I undersand all of this, but for upstreaming we want the root cause, not > > bodges like this. > > > > There is no reason to do what this patch does, the IRQ system is not supposed > > to loose interrupts on migration, if that is happening on your systems it is a > > serious bug that must be root caused. > > Thank you, Jason. > We'll evaluate more on it. If this is in a VM running under qemu - qemu does Lots Of Stuff whenever a MSI-X is changed and that stuff has been buggy before and resulted in lost things. If it is bare metal, I'm shocked. Maybe an IOMMU driver bug in the interrupt remapping? Jason