From: Jason Gunthorpe <jgg@ziepe.ca>
To: Leon Romanovsky <leon@kernel.org>
Cc: Doug Ledford <dledford@redhat.com>,
Leon Romanovsky <leonro@mellanox.com>,
RDMA mailing list <linux-rdma@vger.kernel.org>,
Guy Levi <guyle@mellanox.com>,
Yishai Hadas <yishaih@mellanox.com>,
Yonatan Cohen <yonatanc@mellanox.com>,
Saeed Mahameed <saeedm@mellanox.com>,
linux-netdev <netdev@vger.kernel.org>
Subject: Re: [PATCH rdma-next 0/3] Introduce new mlx5 CQE format
Date: Tue, 29 May 2018 14:05:15 -0600 [thread overview]
Message-ID: <20180529200515.GA26938@ziepe.ca> (raw)
In-Reply-To: <20180527104234.17261-1-leon@kernel.org>
On Sun, May 27, 2018 at 01:42:31PM +0300, Leon Romanovsky wrote:
> From: Leon Romanovsky <leonro@mellanox.com>
>
> Introduce new internal to mlx5 CQE format - mini-CQE. It is a CQE in
> compressed form that holds data needed to extra a single full CQE.
>
> It stride index, byte count and packet checksum.
>
> Thanks
>
> Yonatan Cohen (3):
> net/mlx5: Exposing a new mini-CQE format
> IB/mlx5: Refactor CQE compression response
> IB/mlx5: Introduce a new mini-CQE format
Applied to for-next.
Generally taking new uapi patches that are first the list should have
a few weeks of comment period, but since this is just adding a new bit
to an existing driver private api it seems OK to go this merge window.
Thanks,
Jason
prev parent reply other threads:[~2018-05-29 20:05 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-05-27 10:42 [PATCH rdma-next 0/3] Introduce new mlx5 CQE format Leon Romanovsky
2018-05-27 10:42 ` [PATCH mlx5-next 1/3] net/mlx5: Exposing a new mini-CQE format Leon Romanovsky
2018-05-29 21:01 ` Saeed Mahameed
2018-05-29 21:35 ` Jason Gunthorpe
2018-05-27 10:42 ` [PATCH rdma-next 2/3] IB/mlx5: Refactor CQE compression response Leon Romanovsky
2018-05-27 10:42 ` [PATCH rdma-next 3/3] IB/mlx5: Introduce a new mini-CQE format Leon Romanovsky
2018-05-28 16:11 ` Jason Gunthorpe
2018-05-28 16:52 ` Yishai Hadas
2018-05-28 17:00 ` Jason Gunthorpe
2018-05-29 20:05 ` Jason Gunthorpe [this message]
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=20180529200515.GA26938@ziepe.ca \
--to=jgg@ziepe.ca \
--cc=dledford@redhat.com \
--cc=guyle@mellanox.com \
--cc=leon@kernel.org \
--cc=leonro@mellanox.com \
--cc=linux-rdma@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=saeedm@mellanox.com \
--cc=yishaih@mellanox.com \
--cc=yonatanc@mellanox.com \
/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;
as well as URLs for NNTP newsgroup(s).