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 BDF8CC3A5A0 for ; Mon, 19 Aug 2019 16:05:08 +0000 (UTC) Received: from vger.kernel.org (vger.kernel.org [209.132.180.67]) by mail.kernel.org (Postfix) with ESMTP id 9430220651 for ; Mon, 19 Aug 2019 16:05:08 +0000 (UTC) Authentication-Results: mail.kernel.org; dkim=pass (2048-bit key) header.d=ziepe.ca header.i=@ziepe.ca header.b="OIqsSXPX" Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1726905AbfHSQFH (ORCPT ); Mon, 19 Aug 2019 12:05:07 -0400 Received: from mail-qt1-f196.google.com ([209.85.160.196]:38004 "EHLO mail-qt1-f196.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1726211AbfHSQFE (ORCPT ); Mon, 19 Aug 2019 12:05:04 -0400 Received: by mail-qt1-f196.google.com with SMTP id x4so2456964qts.5 for ; Mon, 19 Aug 2019 09:05:04 -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=qjbUMhoyRlBrB2pmx0yMahiahDUwqPVaQy5IFCKDGeI=; b=OIqsSXPXZbviyknbeplJa6FF5mEXzPBpNrHBLvf0OMF8gfvJD8rMtRaqC2i40w60Q6 0ooems/EWxdnaXQFW36fYWtAjJrDvPcvdsW6YzldSxGpx3VcaW+O5jcOw+TMk3pErFYs OZZSqimYb/Z0K/YmjGgnPZ/vzOFpFweKtucZK/WF6MrI+suDDcwVxza8veuThMPLO+w8 iZcaR2srQpXzJdK9bslrKpXDHhWvtPURyDP47vEQxpRHtAqZyKhlwt3L2C9E3lYyY4zl taZGVkxvxGeQwmccmhEEk92+fRCaHGdoUJkldjTeDQ3ZU5qO2nMjLHql3TBAexJxgM+M nBYQ== 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=qjbUMhoyRlBrB2pmx0yMahiahDUwqPVaQy5IFCKDGeI=; b=DdN6yp8j16nJsA2iotUGamfXXMpZDN/doWeCzj+EONfVTWrHUnLv8m5h8lF4z/j+B3 675WR/K7eMqtFLg/dD3I0mKCYhBP7Qmi9ybxXXNqMa1LWjWMLESeMvmV2lx15rJBKGO9 O/zBbWjPPKYiJrEXZw2czxYwT/TiQ8C3efIOgKWUZ+ZHZCGtcmu6TYoIWh1FAx//D/gw dXMvwlJheNb84c8mlogCwN1Fv6oMPxH8p3nREjII76aIkwalw++uEedO5zyHhnyRIGHt PEy8iIvdZkRULNX8sSBupQMh2acg9yAZw3kPB9J4Vn3jx20+JjT197jNjCF9mZQKLiZZ BLwQ== X-Gm-Message-State: APjAAAWckYJEmM3+oPdTW54fKem0Kt3e0MPePrg+rlPNLeCvexV6/NP/ Gg1WeESFr780OxZfB4TkONQHEg== X-Google-Smtp-Source: APXvYqztyQOS4b1pKjCeXKm705+A0GDuP5UsZRh4JOIvQy8A9jr5ymKEfXY9yahhCbkDHmMgSpDEMw== X-Received: by 2002:aed:3f29:: with SMTP id p38mr21199002qtf.126.1566230703478; Mon, 19 Aug 2019 09:05:03 -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 p38sm9417040qtc.76.2019.08.19.09.05.02 (version=TLS1_2 cipher=ECDHE-RSA-CHACHA20-POLY1305 bits=256/256); Mon, 19 Aug 2019 09:05:02 -0700 (PDT) Received: from jgg by mlx.ziepe.ca with local (Exim 4.90_1) (envelope-from ) id 1hzk9W-0007Mr-AA; Mon, 19 Aug 2019 13:05:02 -0300 Date: Mon, 19 Aug 2019 13:05:02 -0300 From: Jason Gunthorpe To: Bernard Metzler Cc: Geert Uytterhoeven , Doug Ledford , linux-rdma@vger.kernel.org, linux-kernel@vger.kernel.org Subject: Re: Re: Re: Re: [PATCH] RDMA/siw: Fix compiler warnings on 32-bit due to u64/pointer abuse Message-ID: <20190819160502.GI5058@ziepe.ca> References: <20190819150723.GH5058@ziepe.ca> <20190819141856.GG5058@ziepe.ca> <20190819135213.GF5058@ziepe.ca> <20190819122456.GB5058@ziepe.ca> <20190819100526.13788-1-geert@linux-m68k.org> 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-rdma-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-rdma@vger.kernel.org On Mon, Aug 19, 2019 at 03:54:56PM +0000, Bernard Metzler wrote: > Absolutely. But these addresses are conveyed through the > API as unsigned 64 during post_send(), and land in the siw > send queue as is. During send queue processing, these addresses > must be interpreted according to its context and transformed > (casted) back to the callers intention. I frankly do not > know what we can do differently... The representation of > all addresses as unsigned 64 is given. Sorry for the confusion. send work does not have pointers in it, so I'm confused what this is about. Does siw allow userspace to stick an ordinary pointer for the SG list? The code paths here must be totally different, so there should be different types and functions for each case. Jason