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_SANE_1 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 A4C49CA9EC0 for ; Mon, 28 Oct 2019 17:58:06 +0000 (UTC) Received: from vger.kernel.org (vger.kernel.org [209.132.180.67]) by mail.kernel.org (Postfix) with ESMTP id 809E6214E0 for ; Mon, 28 Oct 2019 17:58:06 +0000 (UTC) Authentication-Results: mail.kernel.org; dkim=pass (2048-bit key) header.d=ziepe.ca header.i=@ziepe.ca header.b="S8jXEa+J" Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1730091AbfJ1R6G (ORCPT ); Mon, 28 Oct 2019 13:58:06 -0400 Received: from mail-qt1-f196.google.com ([209.85.160.196]:41143 "EHLO mail-qt1-f196.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1729738AbfJ1R6F (ORCPT ); Mon, 28 Oct 2019 13:58:05 -0400 Received: by mail-qt1-f196.google.com with SMTP id o3so15848054qtj.8 for ; Mon, 28 Oct 2019 10:58:05 -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=RfGx63e795zWqzkl7OD6MawrhXv+b73myPZMFVCO4Z0=; b=S8jXEa+JCu40jvaI17jTeU9YDwoykTkhwkoxVQthNosWMe/5bIpqwe2Bx0dgVKPBrP gJa+7Sibomkr8RsT8tsM1uQMgToXrLC2QzjdPn+Hvq4FDPXPq4ls5xBDe6UdoW3BwV+u s/O+2O5noVobxE+56Z4OtuowY+j3YVUFjJJjmjE69cuykhJX3DMj2eTGwobR2FDa0otH sDvGD+0HOM/GHotngDqZIVwWFrtTuVljVm/5QRXrzkyROFBfVF7DVWVcSHHvUhfAMsTA kHJO0cNtoh8AVr9t806/ufiCy5lWBAm2M29ffAV113HxAW6wCe2AlUMYBklFhe4+ar5i RziQ== 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=RfGx63e795zWqzkl7OD6MawrhXv+b73myPZMFVCO4Z0=; b=S9zAXNMl1AXoeHP/cd+JeQ7EBQvqkBVBoF6pB/NB1Jlg8gj6hdRmFum1NGs6xeW/no 43svBGuyw56zF80as5CCJh2CR0mopa+7hFcFF9eP8YQcr8PlU1XsEvWzX65yYP57heuZ OQFikaMcRqlVMRBeZ7bY7rLO9tUxy3e2FhkQfXa2y1LPXy0EdUUCijUxPDdcCOXv6VDB jLgFHb0QdSCDsU4JWTBTT+kzZNfgdTseaQAkb83GPU9oXWAOSelDHYUhEDk2gGFtnN71 B01H3c2S3+HLkEZIzoJ8aeizMQ06wdwQURXV2zUTJyX1rCwuamuSElWUH7Q86ifbfe/B uHSw== X-Gm-Message-State: APjAAAUt6CDlZ/jjX950GbKCMbRrag6kem076/8CAGxy3eTPFAhBn17u 5lHR/WSxx9c+/x+8sz9aX+5u4A== X-Google-Smtp-Source: APXvYqxCIii4hvhpYVn2rN95KKxgzwwH+NLDrPOiI4tKXACYZsj7cMidJzFHnNVPJhgpsH1+LBtFhA== X-Received: by 2002:ac8:ac4:: with SMTP id g4mr18499459qti.326.1572285484687; Mon, 28 Oct 2019 10:58:04 -0700 (PDT) Received: from ziepe.ca (hlfxns017vw-142-162-113-180.dhcp-dynamic.fibreop.ns.bellaliant.net. [142.162.113.180]) by smtp.gmail.com with ESMTPSA id k17sm4617496qkg.63.2019.10.28.10.58.03 (version=TLS1_2 cipher=ECDHE-RSA-CHACHA20-POLY1305 bits=256/256); Mon, 28 Oct 2019 10:58:04 -0700 (PDT) Received: from jgg by mlx.ziepe.ca with local (Exim 4.90_1) (envelope-from ) id 1iP9HH-0001a4-DN; Mon, 28 Oct 2019 14:58:03 -0300 Date: Mon, 28 Oct 2019 14:58:03 -0300 From: Jason Gunthorpe To: Bart Van Assche Cc: Leon Romanovsky , Doug Ledford , linux-rdma@vger.kernel.org Subject: Re: [PATCH v2 0/4] Fixes related to the DMA max_segment_size parameter Message-ID: <20191028175803.GA6051@ziepe.ca> References: <20191025225830.257535-1-bvanassche@acm.org> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20191025225830.257535-1-bvanassche@acm.org> User-Agent: Mutt/1.9.4 (2018-02-28) Sender: linux-rdma-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-rdma@vger.kernel.org On Fri, Oct 25, 2019 at 03:58:26PM -0700, Bart Van Assche wrote: > Hi Jason, > > These four patches are what I came up with while analyzing a kernel warning > triggered by the ib_srp kernel driver. Please consider these patches for > inclusion in the Linux kernel. > > Thanks, > > Bart. > > Changes compared to v1: > - Restored the dma_set_max_seg_size() call in setup_dma_device(). Reordered > this patch series to keep it bisectable. > > Bart Van Assche (4): > RDMA/core: Fix ib_dma_max_seg_size() > rdma_rxe: Increase DMA max_segment_size parameter > siw: Increase DMA max_segment_size parameter > RDMA/core: Set DMA parameters correctly Applied to for-next, thanks Jason