From: Yishai Hadas <yishaih-LDSdmyG8hGV8YrgS2mwiifqBs+8SCbDb@public.gmane.org>
To: Roland Dreier <roland-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org>,
Utz Bacher <utz.bacher-tA70FqPdS9bQT0dZR+AlfA@public.gmane.org>
Cc: Alexey Ishchuk
<aishchuk-23VcF4HTsmIX0ybBhKVfKdBPR1lH4CV8@public.gmane.org>,
blaschka-23VcF4HTsmIX0ybBhKVfKdBPR1lH4CV8@public.gmane.org,
Gonzalo Muelas Serrano
<gmuelas-tA70FqPdS9bQT0dZR+AlfA@public.gmane.org>,
"linux-rdma-u79uwXL29TY76Z2rM5mHXA@public.gmane.org"
<linux-rdma-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>,
mschwid2-23VcF4HTsmIX0ybBhKVfKdBPR1lH4CV8@public.gmane.org,
Yishai Hadas <yishaih-VPRAkNaXOzVWk0Htik3J/w@public.gmane.org>,
amira-VPRAkNaXOzVWk0Htik3J/w@public.gmane.org
Subject: Re: [PATCH 0/3] DAPL support on s390x platform
Date: Wed, 12 Nov 2014 14:38:49 +0200 [thread overview]
Message-ID: <546354D9.9050601@dev.mellanox.co.il> (raw)
In-Reply-To: <CAL1RGDVLeNCAXrrq8mEhKxcm_z_xwgLUfO_wzhQE9xJz8Lnq7g-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
On 11/12/2014 1:22 AM, Roland Dreier wrote:
> On Wed, Nov 5, 2014 at 7:04 AM, Utz Bacher <utz.bacher-tA70FqPdS9bQT0dZR+AlfA@public.gmane.org> wrote:
>> (B) Status of patches
>> 1. kernel code -- the new system call: reviewed, acked and accepted by the
>> s390x maintainer Martin Schwidefsky (2014/10/13), so we will have that
>> system call in the s390x kernel.
>> 2. libibverbs -- define barriers on s390x: Looking for your feedback. We
>> understand there have been no general objections so far.
>> 3. libmlx4 -- provide MMIO abstraction: reviewed by the Mellanox
>> maintainers and we understand they would apply this once you give the go
>> for the overall set.
>> Previously, a patch to DAPL to build on s390x has been accepted already
>> (Arlin Davis, 2014/09/02).
>>
>> We gave your concern on MMIO handling on s390x serious consideration from
>> various angles, but the page fault handler does not appear workable. OTOH,
>> Mellanox is fine with the MMIO abstraction in libmlx4, and we didn't hear
>> of significant other concerns. With that, could you please consider the
>> patch set again to add s390x to the list of supported platforms? Happy to
>> repost the patches for convenience.
>
> If Mellanox is willing to take on the maintenance burden of changing
> all MMIO access to an inline function, and if you're willing to take
> on the burden of knowing that every new adapter you support means
> tracking down and convincing the maintainer of the driver library,
> then I'm OK with adding the simple barrier patch to libibverbs. Could
> you please send the latest version of that patch to me?
>
The libmlx4 patch should pass some performance regression before it can
be approved, this task is in progress in our side.
> It does seem a little strange to be adding a new system call to
> simulate kernel bypass, but I guess you do what you gotta do...
>
> - R.
> --
> To unsubscribe from this list: send the line "unsubscribe linux-rdma" in
> the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
>
--
To unsubscribe from this list: send the line "unsubscribe linux-rdma" in
the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2014-11-12 12:38 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-10-10 9:34 [PATCH 0/3] DAPL support on s390x platform Alexey Ishchuk
[not found] ` <1412933657-52641-1-git-send-email-aishchuk-23VcF4HTsmIX0ybBhKVfKdBPR1lH4CV8@public.gmane.org>
2014-10-10 9:34 ` [PATCH 1/3] s390/kernel: add system calls for access PCI memory Alexey Ishchuk
[not found] ` <1412933657-52641-2-git-send-email-aishchuk-23VcF4HTsmIX0ybBhKVfKdBPR1lH4CV8@public.gmane.org>
2014-10-12 11:52 ` Shachar Raindel
[not found] ` <f061a36c713c42c9b71530183a6e8644-Vl31pUvGNwELId+1UC+8EGu6+pknBqLbXA4E9RH9d+qIuWR1G4zioA@public.gmane.org>
2014-10-13 8:39 ` Martin Schwidefsky
2014-10-10 9:34 ` [PATCH 2/3] libibverbs: add support for the s390x platform Alexey Ishchuk
2014-10-10 9:34 ` [PATCH 3/3] libmlx4: " Alexey Ishchuk
2014-11-05 15:04 ` [PATCH 0/3] DAPL support on " Utz Bacher
[not found] ` <OF2939B020.E253C5B0-ONC1257D87.0050AE0F-C1257D87.0052C3AA-tA70FqPdS9bQT0dZR+AlfA@public.gmane.org>
2014-11-11 23:22 ` Roland Dreier
[not found] ` <CAL1RGDVLeNCAXrrq8mEhKxcm_z_xwgLUfO_wzhQE9xJz8Lnq7g-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2014-11-12 9:34 ` Martin Schwidefsky
2014-11-12 12:38 ` Yishai Hadas [this message]
[not found] ` <546354D9.9050601-LDSdmyG8hGV8YrgS2mwiifqBs+8SCbDb@public.gmane.org>
2014-12-10 16:27 ` Utz Bacher
[not found] ` <OFA12CE4AE.0DA527AB-ONC1257DAA.0057DC75-C1257DAA.005A6BB7-tA70FqPdS9bQT0dZR+AlfA@public.gmane.org>
2014-12-12 8:19 ` Martin Schwidefsky
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=546354D9.9050601@dev.mellanox.co.il \
--to=yishaih-ldsdmyg8hgv8yrgs2mwiifqbs+8scbdb@public.gmane.org \
--cc=aishchuk-23VcF4HTsmIX0ybBhKVfKdBPR1lH4CV8@public.gmane.org \
--cc=amira-VPRAkNaXOzVWk0Htik3J/w@public.gmane.org \
--cc=blaschka-23VcF4HTsmIX0ybBhKVfKdBPR1lH4CV8@public.gmane.org \
--cc=gmuelas-tA70FqPdS9bQT0dZR+AlfA@public.gmane.org \
--cc=linux-rdma-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=mschwid2-23VcF4HTsmIX0ybBhKVfKdBPR1lH4CV8@public.gmane.org \
--cc=roland-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org \
--cc=utz.bacher-tA70FqPdS9bQT0dZR+AlfA@public.gmane.org \
--cc=yishaih-VPRAkNaXOzVWk0Htik3J/w@public.gmane.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox