From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from 011.lax.mailroute.net (011.lax.mailroute.net [199.89.1.14]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by smtp.subspace.kernel.org (Postfix) with ESMTPS id 702F13AFB19 for ; Wed, 13 May 2026 19:26:29 +0000 (UTC) Authentication-Results: smtp.subspace.kernel.org; arc=none smtp.client-ip=199.89.1.14 ARC-Seal:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1778700390; cv=none; b=QVS59eKC+Rc4U6CbEoDDwMqXehVK9YZtaBPAiKHo37/j+ahylOb5G5TG3FHoXmHoYsmYgCOLDJl2MLajzAqaGMBcgCCs85GKDGtUoOx5PBRVGZsuKJWJAcp/JlGAN6RBZAXecf3cGDW54LXXxFinm3EJqJmMe07itG2iEuP8ABM= ARC-Message-Signature:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1778700390; c=relaxed/simple; bh=+Vf4tBheg5Dj9udBZOD5dz516hHdl/MIrYvPSbtraiw=; h=Message-ID:Date:MIME-Version:Subject:To:Cc:References:From: In-Reply-To:Content-Type; b=FENEqbg4zm/A2u9+mi+2M9f1VZSZXGeno4tp4LZI3ReXC283L+95mSC/icGAWwG5IJeEUR91iQ6bkcAZsaxtzx3TjbM+CkR1iu0UZz1/DJhtn1qdhw4GuaXIZY7P1iAQ/M81M7bnLRTcy3cgXthn6OLNjUTpJ0nD4yoQe1czWAI= ARC-Authentication-Results:i=1; smtp.subspace.kernel.org; dmarc=pass (p=reject dis=none) header.from=acm.org; spf=pass smtp.mailfrom=acm.org; dkim=pass (2048-bit key) header.d=acm.org header.i=@acm.org header.b=DwYfBXLk; arc=none smtp.client-ip=199.89.1.14 Authentication-Results: smtp.subspace.kernel.org; dmarc=pass (p=reject dis=none) header.from=acm.org Authentication-Results: smtp.subspace.kernel.org; spf=pass smtp.mailfrom=acm.org Authentication-Results: smtp.subspace.kernel.org; dkim=pass (2048-bit key) header.d=acm.org header.i=@acm.org header.b="DwYfBXLk" Received: from localhost (localhost [127.0.0.1]) by 011.lax.mailroute.net (Postfix) with ESMTP id 4gG3Nh6Z81z1XM0nq; Wed, 13 May 2026 19:26:28 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=acm.org; h= content-transfer-encoding:content-type:content-type:in-reply-to :from:from:content-language:references:subject:subject :user-agent:mime-version:date:date:message-id:received:received; s=mr01; t=1778700383; x=1781292384; bh=+Vf4tBheg5Dj9udBZOD5dz51 6hHdl/MIrYvPSbtraiw=; b=DwYfBXLkifT0Vd4PFB8APp+umsn8ZUnH55dOs2nD 1Cus7VI79VRmgfXGDkSZlu1YQpiKZQMYh43KFRkSqRyCFWcUwWJCvJh5F2VSAvnK NNUxTAS1IwP3pMYUk2ssEqp2hqDA9ZUGJccXfjXD22PM+hjK9ggSZvLVuuiESKz8 G3ZHUwe55ETwUK0aPBc9LaGgRchSzM7+f/xAr+hgR46VbuRmc9tJgu35+b33M+kH zu/ZW3wM5mZlpEKB7oXWaVJZnSUo5YXvbaDHBUW9Bp6fekNGrYjyl1c7lzmUeZsz heE3NRCP9Bq0+ly+f5s80EsLlV/zci/AlA0BlALSbi/xxA== X-Virus-Scanned: by MailRoute Received: from 011.lax.mailroute.net ([127.0.0.1]) by localhost (011.lax [127.0.0.1]) (mroute_mailscanner, port 10029) with LMTP id wRoLGvXb5Jlw; Wed, 13 May 2026 19:26:23 +0000 (UTC) Received: from [100.119.48.131] (unknown [104.135.180.219]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits) server-digest SHA256) (No client certificate requested) (Authenticated sender: bvanassche@acm.org) by 011.lax.mailroute.net (Postfix) with ESMTPSA id 4gG3NY4P4lz1XM6JP; Wed, 13 May 2026 19:26:21 +0000 (UTC) Message-ID: Date: Wed, 13 May 2026 12:26:20 -0700 Precedence: bulk X-Mailing-List: linux-scsi@vger.kernel.org List-Id: List-Subscribe: List-Unsubscribe: MIME-Version: 1.0 User-Agent: Mozilla Thunderbird Subject: Re: [PATCH v2 1/2] ufs: core: Introduce ufshcd_mcq_poll_n_cqe_lock() To: =?UTF-8?B?UGV0ZXIgV2FuZyAo546L5L+h5Y+LKQ==?= , "martin.petersen@oracle.com" Cc: "vamshigajjela@google.com" , "alok.a.tiwari@oracle.com" , "linux-scsi@vger.kernel.org" , AngeloGioacchino Del Regno , "chenyuan0y@gmail.com" , "ping.gao@samsung.com" , "matthias.bgg@gmail.com" , "James.Bottomley@HansenPartnership.com" References: <20260402171404.3008494-1-bvanassche@acm.org> <20260402171404.3008494-2-bvanassche@acm.org> <459ba5ca0f24ce49fd7de7ae6e014588f40e2445.camel@mediatek.com> Content-Language: en-US From: Bart Van Assche In-Reply-To: <459ba5ca0f24ce49fd7de7ae6e014588f40e2445.camel@mediatek.com> Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: quoted-printable On 5/12/26 11:50 PM, Peter Wang (=E7=8E=8B=E4=BF=A1=E5=8F=8B) wrote: > May I ask if you have any plans to continue upstreaming this patch > in the future? Hi Peter, After I posted this patch series I learned that even processing a single completion can cause interrupts to be disabled for too long. I think the root cause is in F2FS (f2fs_write_end_io()). I have reported this to the F2FS team and I'm waiting for their feedback. After F2FS has been improved I will repeat my measurements and reduce the number of completions processed in interrupt context if that is still necessary. Thanks, Bart.