Received: by 2002:a25:e7d8:0:0:0:0:0 with SMTP id e207csp1598224ybh; Fri, 13 Mar 2020 04:11:06 -0700 (PDT) X-Google-Smtp-Source: ADFU+vvQGl7/450wh2YM6HD21WJ8Uw1yzbGncVsJTmA/1VKBj+fIICws6PDoQKss7EItYoublBph X-Received: by 2002:a54:4585:: with SMTP id z5mr6477661oib.149.1584097866820; Fri, 13 Mar 2020 04:11:06 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1584097866; cv=none; d=google.com; s=arc-20160816; b=X1ZXxeCECac7w+MRvJYnL0LomVqhrbcmTn76ny5jrsS3fam5iJY2OJY0VF/BE3P8fF bWI2kYd/KOgrM9DDfUFU7omHvLKWyWMMELk3n5z6II496xDKuY3a0wQ5oevaAbmvgJ/u QKSuFek2hlSDfq0pfn1vcpJwuEoMg4jSK3CGVgvqQA4reyHHxCFQjOGkzdfF6wjZlsyY DjeN2xSUutcgKX/KEOrWjYS63OOmJxCi/tGrY5NTCmPaxMhMW6he7O9hNi2bK07o8BpH dqfgAoJUeW65lkJgZlf+6qBqhd1vxDPo2RhZk7IEG/VlOQ2IEQofMxRP3uWqyPDZU4xI l6vQ== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:user-agent:in-reply-to :content-disposition:mime-version:references:message-id:subject:cc :to:from:date:dmarc-filter:dkim-signature; bh=4CqveVje8eZtIec9/f8lDvI9y7a9yJdcnoX9VxusUoU=; b=hU8f4lOJ97a2jve28OM33ummYrEUq4+MBRMLlP5QamJTZ4CaKOYXU0LjG00vR7MdRS FdRTnV7FUt6JYgWtPCcJ4PsiH+IVbCJ3RB130mqhNgYwST7P+K0iCXKQpbjARAL6VP3U x+ZxOv1FkU5VpzENDgPUGtaX5xX4bpT8NO2MDSyfEUSZqAP52LWjXgz2ceNzWjqqNTFi qI3Gou8vXdPOpb8q5olg0Cy+O0w+fVBbh12ke8OPjvkJfClcE4v9o4C4r0mZOEbFQGI4 T+Y5I65IDyL+1CDAJeoP6GY9F2N4W1/dDuEBYDqkDDglhJrzHL9UkFdQOQ7OFkG7kHDx FrQg== ARC-Authentication-Results: i=1; mx.google.com; dkim=fail header.i=@mg.codeaurora.org header.s=smtp header.b=vIyx8zVp; 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 Return-Path: Received: from vger.kernel.org (vger.kernel.org. [209.132.180.67]) by mx.google.com with ESMTP id g15si4185770otj.64.2020.03.13.04.10.54; Fri, 13 Mar 2020 04:11:06 -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=fail header.i=@mg.codeaurora.org header.s=smtp header.b=vIyx8zVp; 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 Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1726550AbgCMLJJ (ORCPT + 99 others); Fri, 13 Mar 2020 07:09:09 -0400 Received: from mail27.static.mailgun.info ([104.130.122.27]:26660 "EHLO mail27.static.mailgun.info" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1726414AbgCMLJJ (ORCPT ); Fri, 13 Mar 2020 07:09:09 -0400 DKIM-Signature: a=rsa-sha256; v=1; c=relaxed/relaxed; d=mg.codeaurora.org; q=dns/txt; s=smtp; t=1584097748; h=In-Reply-To: Content-Type: MIME-Version: References: Message-ID: Subject: Cc: To: From: Date: Sender; bh=4CqveVje8eZtIec9/f8lDvI9y7a9yJdcnoX9VxusUoU=; b=vIyx8zVpemwBTmMox6NyLWjzOzppEd8mQXeO0sTwAp5Rnh7KcOe4+TWkq+fehlDVmj6GVxjw UV8ECGP5Sm9UMRv0gwf9Qy9nnWomxN5kEYc6CWED2ImcJ0dK5f2LTA0i8bhGlUrLbDqWjDuo c5TRaoXItSzil0M3bNZEz1tqlJ4= X-Mailgun-Sending-Ip: 104.130.122.27 X-Mailgun-Sid: WyI0MWYwYSIsICJsaW51eC1rZXJuZWxAdmdlci5rZXJuZWwub3JnIiwgImJlOWU0YSJd Received: from smtp.codeaurora.org (ec2-35-166-182-171.us-west-2.compute.amazonaws.com [35.166.182.171]) by mxa.mailgun.org with ESMTP id 5e6b69c5.7f8b3ef91688-smtp-out-n05; Fri, 13 Mar 2020 11:08:53 -0000 (UTC) Received: by smtp.codeaurora.org (Postfix, from userid 1001) id 87E14C44788; Fri, 13 Mar 2020 11:08:52 +0000 (UTC) X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-caf-mail-1.web.codeaurora.org X-Spam-Level: X-Spam-Status: No, score=-1.0 required=2.0 tests=ALL_TRUSTED,SPF_NONE autolearn=unavailable autolearn_force=no version=3.4.0 Received: from codeaurora.org (blr-c-bdr-fw-01_GlobalNAT_AllZones-Outside.qualcomm.com [103.229.19.19]) (using TLSv1.2 with cipher DHE-RSA-AES128-SHA (128/128 bits)) (No client certificate requested) (Authenticated sender: stummala) by smtp.codeaurora.org (Postfix) with ESMTPSA id D12A8C433D2; Fri, 13 Mar 2020 11:08:49 +0000 (UTC) DMARC-Filter: OpenDMARC Filter v1.3.2 smtp.codeaurora.org D12A8C433D2 Authentication-Results: aws-us-west-2-caf-mail-1.web.codeaurora.org; dmarc=none (p=none dis=none) header.from=codeaurora.org Authentication-Results: aws-us-west-2-caf-mail-1.web.codeaurora.org; spf=none smtp.mailfrom=stummala@codeaurora.org Date: Fri, 13 Mar 2020 16:38:46 +0530 From: Sahitya Tummala To: Chao Yu Cc: Jaegeuk Kim , linux-f2fs-devel@lists.sourceforge.net, linux-kernel@vger.kernel.org, stummala@codeaurora.org Subject: Re: [PATCH] f2fs: fix long latency due to discard during umount Message-ID: <20200313110846.GL20234@codeaurora.org> References: <1584011671-20939-1-git-send-email-stummala@codeaurora.org> <20200313033912.GJ20234@codeaurora.org> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.21 (2010-09-15) Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Fri, Mar 13, 2020 at 02:30:55PM +0800, Chao Yu wrote: > On 2020/3/13 11:39, Sahitya Tummala wrote: > > On Fri, Mar 13, 2020 at 10:20:04AM +0800, Chao Yu wrote: > >> On 2020/3/12 19:14, Sahitya Tummala wrote: > >>> F2FS already has a default timeout of 5 secs for discards that > >>> can be issued during umount, but it can take more than the 5 sec > >>> timeout if the underlying UFS device queue is already full and there > >>> are no more available free tags to be used. In that case, submit_bio() > >>> will wait for the already queued discard requests to complete to get > >>> a free tag, which can potentially take way more than 5 sec. > >>> > >>> Fix this by submitting the discard requests with REQ_NOWAIT > >>> flags during umount. This will return -EAGAIN for UFS queue/tag full > >>> scenario without waiting in the context of submit_bio(). The FS can > >>> then handle these requests by retrying again within the stipulated > >>> discard timeout period to avoid long latencies. > >>> > >>> Signed-off-by: Sahitya Tummala > >>> --- > >>> fs/f2fs/segment.c | 14 +++++++++++++- > >>> 1 file changed, 13 insertions(+), 1 deletion(-) > >>> > >>> diff --git a/fs/f2fs/segment.c b/fs/f2fs/segment.c > >>> index fb3e531..a06bbac 100644 > >>> --- a/fs/f2fs/segment.c > >>> +++ b/fs/f2fs/segment.c > >>> @@ -1124,10 +1124,13 @@ static int __submit_discard_cmd(struct f2fs_sb_info *sbi, > >>> struct discard_cmd_control *dcc = SM_I(sbi)->dcc_info; > >>> struct list_head *wait_list = (dpolicy->type == DPOLICY_FSTRIM) ? > >>> &(dcc->fstrim_list) : &(dcc->wait_list); > >>> - int flag = dpolicy->sync ? REQ_SYNC : 0; > >>> + int flag; > >>> block_t lstart, start, len, total_len; > >>> int err = 0; > >>> > >>> + flag = dpolicy->sync ? REQ_SYNC : 0; > >>> + flag |= dpolicy->type == DPOLICY_UMOUNT ? REQ_NOWAIT : 0; > >>> + > >>> if (dc->state != D_PREP) > >>> return 0; > >>> > >>> @@ -1203,6 +1206,11 @@ static int __submit_discard_cmd(struct f2fs_sb_info *sbi, > >>> bio->bi_end_io = f2fs_submit_discard_endio; > >>> bio->bi_opf |= flag; > >>> submit_bio(bio); > >>> + if ((flag & REQ_NOWAIT) && (dc->error == -EAGAIN)) { > >> > >> If we want to update dc->state, we need to cover it with dc->lock. > > > > Sure, will update it. > > > >> > >>> + dc->state = D_PREP; > >> > >> BTW, one dc can be referenced by multiple bios, so dc->state could be updated to > >> D_DONE later by f2fs_submit_discard_endio(), however we just relocate it to > >> pending list... which is inconsistent status. > > > > In that case dc->bio_ref will reflect it and until it becomes 0, the dc->state > > will not be updated to D_DONE in f2fs_submit_discard_endio()? > > __submit_discard_cmd() > lock() > dc->state = D_SUBMIT; > dc->bio_ref++; > unlock() > ... > submit_bio() > f2fs_submit_discard_endio() > dc->error = -EAGAIN; > lock() > dc->bio_ref--; > > dc->state = D_PREP; > > dc->state = D_DONE; > unlock() > > So finally, dc's state is D_DONE, and it's in wait list, then will be relocated > to pending list. In case of queue full, f2fs_submit_discard_endio() will not be called asynchronously. It will be called in the context of submit_bio() itself. So by the time, submit_bio returns dc->error will be -EAGAIN and dc->state will be D_DONE. submit_bio() ->blk_mq_make_request ->blk_mq_get_request() ->bio_wouldblock_error() (called due to queue full) ->bio_endio() Thanks, > > > > > Thanks, > > > >> > >> Thanks, > >> > >>> + err = dc->error; > >>> + break; > >>> + } > >>> > >>> atomic_inc(&dcc->issued_discard); > >>> > >>> @@ -1510,6 +1518,10 @@ static int __issue_discard_cmd(struct f2fs_sb_info *sbi, > >>> } > >>> > >>> __submit_discard_cmd(sbi, dpolicy, dc, &issued); > >>> + if (dc->error == -EAGAIN) { > >>> + congestion_wait(BLK_RW_ASYNC, HZ/50); > >>> + __relocate_discard_cmd(dcc, dc); > >>> + } > >>> > >>> if (issued >= dpolicy->max_requests) > >>> break; > >>> > > -- -- Sent by a consultant of the Qualcomm Innovation Center, Inc. The Qualcomm Innovation Center, Inc. is a member of the Code Aurora Forum.