Received: by 2002:a25:6193:0:0:0:0:0 with SMTP id v141csp3822156ybb; Mon, 6 Apr 2020 16:51:36 -0700 (PDT) X-Google-Smtp-Source: APiQypIbx4tz5htYxiD4xPYTD6qnC1ie7pkKAbqW3BAbaFIN4xXcxILxk59jt2RUT3sPGu9Qx8P0 X-Received: by 2002:aca:ef82:: with SMTP id n124mr1363793oih.73.1586217095970; Mon, 06 Apr 2020 16:51:35 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1586217095; cv=none; d=google.com; s=arc-20160816; b=Djx8oV6QEg+Fe1Wf7snda7dklYX2z6EFKsGKDpllN2skgspHJPt9+JQYWcZO5GxByq +RSunPNPG1IKbQNawbRV8T5bciGQ5rfP0Ltpjndd+pCX/fsvy4wh+HJanzog6Y4XwvqW DDcGGPsl9sIzCSfYKl7Jhfc3b9GKt3GIJQ86lF+9Z1USOnNiRrwtNZrLor+cW8+JO+3S WpG+18x2TSsScLvQIUHqUv72QhECpBOjGUQmjbBYqjSqu0yUgAa63SnXUnZVJf5MbSvF gbvkBnMaySj3MQFYcQ6IRO+w8uNqItUb8wecuQ0BNB+b14JtlAHe3ADSpLn98ENWoFmn kVuw== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:dkim-signature:content-language :content-transfer-encoding:in-reply-to:mime-version:user-agent:date :message-id:references:cc:to:from:subject; bh=eDmJhImp44bFVlJm/Ozt/iGy5h5LhIidOSGnknxyi9s=; b=YiVgwmA8SzW5x2DICaflO5jqzjWpL1RsRXHDRLattwnbCYXSLCpoMX/Z7/cS4Cx3GC 3TkjILI01nQCJw+Pnjecsn2QtmyyTOk8UdN2dJnlQNuZtA388c2owh/Yi914bG1wXlKf 1LD84WCp41YQtIuWcVXoXNiwTOPc7J712oRQTgoF17Q/bi9lXOTpQV20U2a4DTplyJL0 TB94mRTjiLKRBZYlIevO1zO161elY/BpGFEo4gTNov3lvCNF+taZe2hMADx8KzFIZhkC 8jFKPL1sPQhP7JOTx/vl45fB0nOFh4YwemsiX8XkocPv4UexL80kNUknVdiNgT0kqKqC G57g== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@nvidia.com header.s=n1 header.b=R8aaP7mt; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=pass (p=NONE sp=NONE dis=NONE) header.from=nvidia.com Return-Path: Received: from vger.kernel.org (vger.kernel.org. [209.132.180.67]) by mx.google.com with ESMTP id z6si463205otm.218.2020.04.06.16.51.23; Mon, 06 Apr 2020 16:51:35 -0700 (PDT) Received-SPF: pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) client-ip=209.132.180.67; Authentication-Results: mx.google.com; dkim=pass header.i=@nvidia.com header.s=n1 header.b=R8aaP7mt; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=pass (p=NONE sp=NONE dis=NONE) header.from=nvidia.com Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1726386AbgDFXuv (ORCPT + 99 others); Mon, 6 Apr 2020 19:50:51 -0400 Received: from hqnvemgate26.nvidia.com ([216.228.121.65]:12079 "EHLO hqnvemgate26.nvidia.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1726287AbgDFXuu (ORCPT ); Mon, 6 Apr 2020 19:50:50 -0400 Received: from hqpgpgate101.nvidia.com (Not Verified[216.228.121.13]) by hqnvemgate26.nvidia.com (using TLS: TLSv1.2, DES-CBC3-SHA) id ; Mon, 06 Apr 2020 16:50:37 -0700 Received: from hqmail.nvidia.com ([172.20.161.6]) by hqpgpgate101.nvidia.com (PGP Universal service); Mon, 06 Apr 2020 16:50:50 -0700 X-PGP-Universal: processed; by hqpgpgate101.nvidia.com on Mon, 06 Apr 2020 16:50:50 -0700 Received: from DRHQMAIL107.nvidia.com (10.27.9.16) by HQMAIL111.nvidia.com (172.20.187.18) with Microsoft SMTP Server (TLS) id 15.0.1473.3; Mon, 6 Apr 2020 23:50:49 +0000 Received: from [10.2.164.193] (172.20.13.39) by DRHQMAIL107.nvidia.com (10.27.9.16) with Microsoft SMTP Server (TLS) id 15.0.1473.3; Mon, 6 Apr 2020 23:50:48 +0000 Subject: Re: [RFC PATCH v6 6/9] media: tegra: Add Tegra210 Video input driver From: Sowjanya Komatineni To: Dmitry Osipenko , , , , , , CC: , , , , , References: <1585963507-12610-1-git-send-email-skomatineni@nvidia.com> <1585963507-12610-7-git-send-email-skomatineni@nvidia.com> <200bb96e-2d07-764f-9e14-55538dc742fd@gmail.com> <23bfab09-b464-6e51-9843-06d13000e9b9@nvidia.com> <08cd31d5-e8b9-4d3a-fb0e-0e4462947d96@nvidia.com> <12a834ac-52b1-6dc0-7d3a-3e6a1fa85a2a@gmail.com> <760d071e-0cbc-b3eb-9231-fb9f9ecb44a6@nvidia.com> <9e317f65-8a02-3b15-cfec-8e0d8374130e@gmail.com> <97b35910-4c93-123a-43a0-eb14476ed0f3@nvidia.com> Message-ID: <323fe80a-f6b7-d36d-f975-92706411541f@nvidia.com> Date: Mon, 6 Apr 2020 16:50:47 -0700 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:60.0) Gecko/20100101 Thunderbird/60.9.0 MIME-Version: 1.0 In-Reply-To: <97b35910-4c93-123a-43a0-eb14476ed0f3@nvidia.com> X-Originating-IP: [172.20.13.39] X-ClientProxiedBy: HQMAIL107.nvidia.com (172.20.187.13) To DRHQMAIL107.nvidia.com (10.27.9.16) Content-Type: text/plain; charset="utf-8"; format=flowed Content-Transfer-Encoding: quoted-printable Content-Language: en-US DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=nvidia.com; s=n1; t=1586217037; bh=eDmJhImp44bFVlJm/Ozt/iGy5h5LhIidOSGnknxyi9s=; h=X-PGP-Universal:Subject:From:To:CC:References:Message-ID:Date: User-Agent:MIME-Version:In-Reply-To:X-Originating-IP: X-ClientProxiedBy:Content-Type:Content-Transfer-Encoding: Content-Language; b=R8aaP7mtuw1y+5nF1B+xXov0MUpCQVBj3FubrfHZjXD2fZFDNMWYBDPqwvqw6ojcI zp7VWcwEeprfi5pWp8xppmHdiO0HS2It26W2IYVyfaNCwnsJYu1m8bYptHO+fnBfnt 1MryZbZ7pchpugekljjHNaf1XzoF7ynrmSbPaLe2DhJBZ5NuJanrZF/p1m3gUdgk0/ wZD0f2pemZtRaHkMubXBrJy9VSPie4mPt2gR1zgln7uGjWd3tjm8z2v1cLd0am3geS lBzeR4cgQ4naX8kfZGhovq6/CyWZOdxc12qcSXNi/tKNTxzLUBLGd1mlY6+Z6FlSlF ixwWfMznhJYQA== Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On 4/6/20 4:48 PM, Sowjanya Komatineni wrote: > > On 4/6/20 4:18 PM, Dmitry Osipenko wrote: >> External email: Use caution opening links or attachments >> >> >> 07.04.2020 01:07, Sowjanya Komatineni =D0=BF=D0=B8=D1=88=D0=B5=D1=82: >>> On 4/6/20 3:00 PM, Sowjanya Komatineni wrote: >>>> On 4/6/20 2:39 PM, Sowjanya Komatineni wrote: >>>>> On 4/6/20 2:15 PM, Sowjanya Komatineni wrote: >>>>>> On 4/6/20 2:11 PM, Dmitry Osipenko wrote: >>>>>>> External email: Use caution opening links or attachments >>>>>>> >>>>>>> >>>>>>> 07.04.2020 00:02, Sowjanya Komatineni =D0=BF=D0=B8=D1=88=D0=B5=D1= =82: >>>>>>>>>>>>> Am I understanding correctly that this thread will take 100% >>>>>>>>>>>>> CPU, >>>>>>>>>>>>> spinning here, if more than 2 frame-captures queued? >>>>>>>>>>>> on more than 2 frames captures, it breaks thread and on next >>>>>>>>>>>> wakeup it >>>>>>>>>>>> continues >>>>>>>>>>> The wait_event() won't wait if condition is true. >>>>>>>>>> condition is checked when waitqueue is woken up >>>>>>>>> https://elixir.bootlin.com/linux/v5.6.2/source/include/linux/wait= .h#L462=20 >>>>>>>>> >>>>>>>>> >>>>>>>> process is put to sleep until the condition evaluates to true or >>>>>>>> signal >>>>>>>> is received. >>>>>>>> >>>>>>>> condition is checked each time the waitqueue head is woken up. >>>>>>> This is a wrong assumption in accordance to the code. >>>> process is in sleep until the condition is evaluated and when >>>> condition is true wakeup still happens only when wake_up on waitqueue >>>> is called >>>> >>>> This is the reason for using this to prevent blocking while waiting >>>> for the buffers. >>> w.r.t capture list update, wakeup happens when wake_up on waitqueue is >>> called. >>> >>> wakeup also happens on kthread stop signal event. >>> >>>> >>>>>> when every buffer is available as long as we are in streaming, we >>>>>> should process it. >>>>>> >>>>>> So if wake up happens when list has buffer, it will be processed but >>>>>> at a time we limit processing 2 simultaneous buffer capture starts >>>>>> only. >>>>>> >>>>> Fixing typo. >>>>> >>>>> I meant when ever buffer is available as long as we are in streaming, >>>>> we should process it. >>>>> >>>>> So capture thread processes as long as buffers are available from >>>>> user space limiting 2 simultaneous trigger of captures and thread >>>>> will be in sleep when capture buffers list is empty or no stop thread >>>>> is signaled. >> IIUC, the waiting won't happen if more than 2 captures are queued and >> thread will be spinning until captures are processed. >> >> I think you need a semaphore with resource count =3D 2. > we hold on to issuing capture if more than 2 buffers are queued and it=20 > continues only after fifo has min 1 slot empty caps_inflight gets updated based on requested frame and finished frames=20 and capture will happen only for 2 frames at a time but not more