From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org X-Spam-Level: X-Spam-Status: No, score=-0.8 required=3.0 tests=HEADER_FROM_DIFFERENT_DOMAINS, MAILING_LIST_MULTI,SPF_HELO_NONE,SPF_PASS autolearn=no autolearn_force=no version=3.4.0 Received: from mail.kernel.org (mail.kernel.org [198.145.29.99]) by smtp.lore.kernel.org (Postfix) with ESMTP id 2CB8FC432C0 for ; Mon, 18 Nov 2019 14:05:56 +0000 (UTC) Received: from vger.kernel.org (vger.kernel.org [209.132.180.67]) by mail.kernel.org (Postfix) with ESMTP id 0B15F20722 for ; Mon, 18 Nov 2019 14:05:56 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1727116AbfKROFz (ORCPT ); Mon, 18 Nov 2019 09:05:55 -0500 Received: from mx2.suse.de ([195.135.220.15]:51548 "EHLO mx1.suse.de" rhost-flags-OK-OK-OK-FAIL) by vger.kernel.org with ESMTP id S1726654AbfKROFy (ORCPT ); Mon, 18 Nov 2019 09:05:54 -0500 X-Virus-Scanned: by amavisd-new at test-mx.suse.de Received: from relay2.suse.de (unknown [195.135.220.254]) by mx1.suse.de (Postfix) with ESMTP id C2174ADDD; Mon, 18 Nov 2019 14:05:52 +0000 (UTC) Date: Mon, 18 Nov 2019 14:05:51 +0000 From: Luis Henriques To: Jeff Layton Cc: Sage Weil , Ilya Dryomov , "Yan, Zheng" , Gregory Farnum , ceph-devel@vger.kernel.org, linux-kernel@vger.kernel.org Subject: Re: [RFC PATCH v3] ceph: add new obj copy OSD Op Message-ID: <20191118140551.GA8951@hermes.olymp> References: <20191118120935.7013-1-lhenriques@suse.com> <3dc2df0ba5776fb0f7aaac3a099a938823ed0ebf.camel@kernel.org> MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Disposition: inline Content-Transfer-Encoding: 8bit In-Reply-To: <3dc2df0ba5776fb0f7aaac3a099a938823ed0ebf.camel@kernel.org> Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Mon, Nov 18, 2019 at 08:12:39AM -0500, Jeff Layton wrote: > On Mon, 2019-11-18 at 12:09 +0000, Luis Henriques wrote: > > Hi, > > > > Before going ahead with a pull-request for ceph I would like to make sure > > we're all on the same page regarding the final fix for this problem. > > Thus, following this email, I'm sending 2 patches: one for ceph OSDs and > > the another for the kernel client. > > > > * osd: add new 'copy-from-notrunc' operation > > This patch shall be applied to ceph master after reverting commit > > ba152435fd85 ("osd: add flag to prevent truncate_seq copy in copy-from > > operation"). It adds a new operation that will be exactly the same as > > the original 'copy-from' operation, but with the extra 2 parameters > > (truncate_{seq,size}) > > > > * ceph: switch copy_file_range to 'copy-from-notrunc' operation > > This will make the kernel client use the new OSD op in > > copy_file_range. One extra thing that could probably be added is > > changing the mount options to NOCOPYFROM if the first call to > > ceph_osdc_copy_from() fails. > > > > I probably wouldn't change the mount options to be different from what > was initially specified. How about just disable copy_file_range > internally for that superblock, and then pr_notice a message that says > that copy_file_range is being autodisabled. If they mount with '-o > nocopyfrom' that will make the warning go away. Ok, that makes sense. I'll include this in the next rev, which will probably be sent only after the pull-request for ceph goes in (assuming the OSD patch won't need any major rework). > > Does this look good, or did I missed something from the previous > > discussion? > > > > (One advantage of this approach: the OSD patch can be easily backported!) > > > > Yep, I think this looks like a _much_ simpler approach to the problem. Agreed! Cheers, -- Luís