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=-2.4 required=3.0 tests=DKIM_SIGNED,DKIM_VALID, DKIM_VALID_AU,HEADER_FROM_DIFFERENT_DOMAINS,MAILING_LIST_MULTI,SPF_HELO_NONE, SPF_PASS,USER_AGENT_MUTT autolearn=ham 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 940A8C31E45 for ; Thu, 13 Jun 2019 15:12:26 +0000 (UTC) Received: from vger.kernel.org (vger.kernel.org [209.132.180.67]) by mail.kernel.org (Postfix) with ESMTP id 6D88920449 for ; Thu, 13 Jun 2019 15:12:26 +0000 (UTC) Authentication-Results: mail.kernel.org; dkim=pass (2048-bit key) header.d=ziepe.ca header.i=@ziepe.ca header.b="JRz6imxO" Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S2388214AbfFMPMZ (ORCPT ); Thu, 13 Jun 2019 11:12:25 -0400 Received: from mail-qk1-f194.google.com ([209.85.222.194]:46306 "EHLO mail-qk1-f194.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S2388158AbfFMPMV (ORCPT ); Thu, 13 Jun 2019 11:12:21 -0400 Received: by mail-qk1-f194.google.com with SMTP id x18so975562qkn.13 for ; Thu, 13 Jun 2019 08:12:20 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=ziepe.ca; s=google; h=date:from:to:cc:subject:message-id:references:mime-version :content-disposition:in-reply-to:user-agent; bh=R4sEx9DRCkbOcqkLsi6Jkv1GflPMZb75UMnrOJnbtJI=; b=JRz6imxOTGsNuMS76M162KvumiMVyYkKXhz/IAFwKjp3Igi0hICl/m4BUGOuw61YG6 Pf3He7hg9Kt6x6X1WZuq8bUrqc1a1W2UmAo8VaUwVPA2GdvPEx7a5YMbLY0nfJoFWaQM YEbV9dRjW/drtmRraCujxYyThEP6QtwiSJs3iYcbutlXVk7Z5dASy1/Oy0G/oorjue0j RzaH6Drn7BTg39I+BUiwTL6fije0cyR1reQqzW1AIca5v1agyVprI5RgkLHLmKlYW9Fi 0n1zTcJtV1luwZoUboeqFK2xDSzt81BhwHG/KONzmn78w16+WuqvsJOUxxwdcX8amTie g0WA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:date:from:to:cc:subject:message-id:references :mime-version:content-disposition:in-reply-to:user-agent; bh=R4sEx9DRCkbOcqkLsi6Jkv1GflPMZb75UMnrOJnbtJI=; b=XXXXCzVEkrtDz1iFPu7QFUDTWwNMRFsQSS6N8nIaY7R0UsFo1yZV5yio17/MLaUy8C QdfXewudFIDpJxEVISbeoGy0xvNuO+1sQvh9ugCiehq9dq492wE/ShHxIsVwIoA+aJ24 2THISNkbmm3Qi7DVq3TfPHKh8KUwOjOC5pIRwN2qOf5NnoTecYyfCSG72R40kKWzGt4Z hdS55m6RAMSiIKzPcZ3wvHK62HK6/weQzX+pKEg263CjzYFLD+VnnjJ9xniWoXcNswNW 942pzCLO4ptfZdUq1CwzLXYUS1swwZUSO9WPe9IPbUylEqCD+jOAVIlGQx4suTqIhRG3 z4Rw== X-Gm-Message-State: APjAAAWxD4ON0KYKdAumiO5sEqyU2GZnb59rwxUwWfuuL+FTthuUOpPA 5SSsKeei2heCXM/oWYRmVK0mLR90EuHSXg== X-Google-Smtp-Source: APXvYqzM9yCChTgMP3KlIhiG1BK19OOrfQlMOx6JZlNrolhLErYOjGfGuCWD8w4PBuxWllsDgHA6QA== X-Received: by 2002:a37:e506:: with SMTP id e6mr3810214qkg.229.1560438740039; Thu, 13 Jun 2019 08:12:20 -0700 (PDT) Received: from ziepe.ca (hlfxns017vw-156-34-55-100.dhcp-dynamic.fibreop.ns.bellaliant.net. [156.34.55.100]) by smtp.gmail.com with ESMTPSA id n10sm1577550qke.72.2019.06.13.08.12.19 (version=TLS1_2 cipher=ECDHE-RSA-CHACHA20-POLY1305 bits=256/256); Thu, 13 Jun 2019 08:12:19 -0700 (PDT) Received: from jgg by mlx.ziepe.ca with local (Exim 4.90_1) (envelope-from ) id 1hbROk-0001qR-Po; Thu, 13 Jun 2019 12:12:18 -0300 Date: Thu, 13 Jun 2019 12:12:18 -0300 From: Jason Gunthorpe To: Dan Williams Cc: Ira Weiny , Jan Kara , Theodore Ts'o , Jeff Layton , Dave Chinner , Matthew Wilcox , linux-xfs , Andrew Morton , John Hubbard , =?utf-8?B?SsOpcsO0bWU=?= Glisse , linux-fsdevel , Linux Kernel Mailing List , linux-nvdimm , linux-ext4 , Linux MM Subject: Re: [PATCH RFC 00/10] RDMA/FS DAX truncate proposal Message-ID: <20190613151218.GB22901@ziepe.ca> References: <20190606222228.GB11698@iweiny-DESK2.sc.intel.com> <20190607103636.GA12765@quack2.suse.cz> <20190607121729.GA14802@ziepe.ca> <20190607145213.GB14559@iweiny-DESK2.sc.intel.com> <20190612102917.GB14578@quack2.suse.cz> <20190612114721.GB3876@ziepe.ca> <20190612120907.GC14578@quack2.suse.cz> <20190612191421.GM3876@ziepe.ca> <20190612221336.GA27080@iweiny-DESK2.sc.intel.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.9.4 (2018-02-28) Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Wed, Jun 12, 2019 at 03:54:19PM -0700, Dan Williams wrote: > > > My preference would be to avoid this scenario, but if it is really > > > necessary, we could probably build it with some work. > > > > > > The only case we use it today is forced HW hot unplug, so it is rarely > > > used and only for an 'emergency' like use case. > > > > I'd really like to avoid this as well. I think it will be very confusing for > > RDMA apps to have their context suddenly be invalid. I think if we have a way > > for admins to ID who is pinning a file the admin can take more appropriate > > action on those processes. Up to and including killing the process. > > Can RDMA context invalidation, "device disassociate", be inflicted on > a process from the outside? Yes, but it is currently only applied to the entire device - ie you do 'rmmod mlx5_ib' and all the running user space process see that their FD has moved to some error and the device is broken. Targetting the disassociate of only a single FD would be a new thing. Jason