From: Doug Ledford <dledford-H+wXaHxf7aLQT0dZR+AlfA@public•gmane.org>
To: Saeed Mahameed <saeedm-VPRAkNaXOzVWk0Htik3J/w@public•gmane.org>,
"David S. Miller" <davem-fT/PcQaiUtIeIZ0/mPfg9Q@public•gmane.org>
Cc: netdev-u79uwXL29TY76Z2rM5mHXA@public•gmane.org,
linux-rdma-u79uwXL29TY76Z2rM5mHXA@public•gmane.org,
Leon Romanovsky <leonro-VPRAkNaXOzVWk0Htik3J/w@public•gmane.org>,
Eli Cohen <eli-VPRAkNaXOzVWk0Htik3J/w@public•gmane.org>,
Matan Barak <matanb-VPRAkNaXOzVWk0Htik3J/w@public•gmane.org>,
Leon Romanovsky <leon-DgEjT+Ai2ygdnm+yROfE0A@public•gmane.org>
Subject: Re: [for-next V2 08/10] IB/mlx5: Allow future extension of libmlx5 input data
Date: Mon, 09 Jan 2017 23:24:37 -0500 [thread overview]
Message-ID: <1484022277.2149.4.camel@redhat.com> (raw)
In-Reply-To: <1483890891-8767-9-git-send-email-saeedm-VPRAkNaXOzVWk0Htik3J/w@public.gmane.org>
[-- Attachment #1: Type: text/plain, Size: 776 bytes --]
On Sun, 2017-01-08 at 17:54 +0200, Saeed Mahameed wrote:
> From: Eli Cohen <eli-VPRAkNaXOzVWk0Htik3J/w@public•gmane.org>
>
> Current check requests that new fields in struct
> mlx5_ib_alloc_ucontext_req_v2 that are not known to the driver be
> zero.
> This was introduced so new libraries passing additional information
> to
> the kernel through struct mlx5_ib_alloc_ucontext_req_v2 will be
> notified
> by old kernels that do not support their request by failing the
> operation. This schecme is problematic since it requires libmlx5 to
^ Typo
--
Doug Ledford <dledford-H+wXaHxf7aLQT0dZR+AlfA@public•gmane.org>
GPG KeyID: B826A3330E572FDD
Key fingerprint = AE6B 1BDA 122B 23B4 265B 1274 B826 A333 0E57 2FDD
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 819 bytes --]
next prev parent reply other threads:[~2017-01-10 4:24 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-01-08 15:54 [for-next V2 00/10][pull request] Mellanox 100G mlx5 4K UAR support Saeed Mahameed
2017-01-08 15:54 ` [for-next V2 02/10] IB/mlx5: Fix error handling order in create_kernel_qp Saeed Mahameed
[not found] ` <1483890891-8767-1-git-send-email-saeedm-VPRAkNaXOzVWk0Htik3J/w@public.gmane.org>
2017-01-08 15:54 ` [for-next V2 01/10] IB/mlx5: Fix kernel to user leak prevention logic Saeed Mahameed
2017-01-08 15:54 ` [for-next V2 03/10] mlx5: Fix naming convention with respect to UARs Saeed Mahameed
2017-01-08 15:54 ` [for-next V2 04/10] IB/mlx5: Fix retrieval of index to first hi class bfreg Saeed Mahameed
2017-01-08 15:54 ` [for-next V2 05/10] net/mlx5: Introduce blue flame register allocator Saeed Mahameed
2017-01-08 15:54 ` [for-next V2 06/10] net/mlx5: Add interface to get reference to a UAR Saeed Mahameed
2017-01-08 17:05 ` Yuval Shaia
[not found] ` <20170108170539.GA6323-Hxa29pjIrETlQW142y8m19+IiqhCXseY@public.gmane.org>
2017-01-09 8:31 ` Saeed Mahameed
[not found] ` <CALzJLG-yiZfa6J0WciFPowfF2LWrXAqCKc4ETu4x=ZJdn+CfDA-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2017-01-09 15:47 ` David Miller
[not found] ` <20170109.104722.2246652236667186272.davem-fT/PcQaiUtIeIZ0/mPfg9Q@public.gmane.org>
2017-01-09 16:05 ` Saeed Mahameed
2017-01-09 16:06 ` David Miller
2017-01-08 15:54 ` [for-next V2 08/10] IB/mlx5: Allow future extension of libmlx5 input data Saeed Mahameed
[not found] ` <1483890891-8767-9-git-send-email-saeedm-VPRAkNaXOzVWk0Htik3J/w@public.gmane.org>
2017-01-10 4:24 ` Doug Ledford [this message]
2017-01-08 15:54 ` [for-next V2 07/10] IB/mlx5: Use blue flame register allocator in mlx5_ib Saeed Mahameed
2017-01-08 15:54 ` [for-next V2 09/10] IB/mlx5: Support 4k UAR for libmlx5 Saeed Mahameed
2017-01-08 15:54 ` [for-next V2 10/10] net/mlx5: Activate support for 4K UARs Saeed Mahameed
2017-01-10 4:29 ` [for-next V2 00/10][pull request] Mellanox 100G mlx5 4K UAR support Doug Ledford
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=1484022277.2149.4.camel@redhat.com \
--to=dledford-h+wxahxf7alqt0dzr+alfa@public$(echo .)gmane.org \
--cc=davem-fT/PcQaiUtIeIZ0/mPfg9Q@public$(echo .)gmane.org \
--cc=eli-VPRAkNaXOzVWk0Htik3J/w@public$(echo .)gmane.org \
--cc=leon-DgEjT+Ai2ygdnm+yROfE0A@public$(echo .)gmane.org \
--cc=leonro-VPRAkNaXOzVWk0Htik3J/w@public$(echo .)gmane.org \
--cc=linux-rdma-u79uwXL29TY76Z2rM5mHXA@public$(echo .)gmane.org \
--cc=matanb-VPRAkNaXOzVWk0Htik3J/w@public$(echo .)gmane.org \
--cc=netdev-u79uwXL29TY76Z2rM5mHXA@public$(echo .)gmane.org \
--cc=saeedm-VPRAkNaXOzVWk0Htik3J/w@public$(echo .)gmane.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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