DPDK patches and discussions
 help / color / mirror / Atom feed
From: Shahaf Shuler <shahafs@mellanox.com>
To: Yongseok Koh <yskoh@mellanox.com>
Cc: "dev@dpdk.org" <dev@dpdk.org>,
	"stephen@networkplumber.org" <stephen@networkplumber.org>
Subject: Re: [dpdk-dev] [PATCH v2] net/mlx5: check Tx queue size overflow
Date: Wed, 1 May 2019 06:10:38 +0000	[thread overview]
Message-ID: <AM0PR0502MB3795C08E031FD749A507D889C33B0@AM0PR0502MB3795.eurprd05.prod.outlook.com> (raw)
In-Reply-To: <C6465571-B130-4798-A7DD-75D8630E8900@mellanox.com>

Wednesday, May 1, 2019 4:16 AM, Yongseok Koh:
> Subject: Re: [PATCH v2] net/mlx5: check Tx queue size overflow
> 
> 
> > On Apr 30, 2019, at 6:01 PM, Yongseok Koh <yskoh@mellanox.com> wrote:
> >
> > If Tx packet inlining is enabled, rdma-core library should allocate
> > large Tx WQ enough to support it. It is better for PMD to calculate
> > the size of WQ based on the parameters and return error with
> > appropriate message if it exceeds the device capability.
> >
> > Cc:stable@dpdk.org
> 
> Shahaf,
> There's a checkpatch warning. Please put a space after ':' if you merge it.

Changed and applied to next-net-mlx, thanks.

  parent reply	other threads:[~2019-05-01  6:10 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-04-30 19:04 [dpdk-dev] [PATCH] " Yongseok Koh
2019-04-30 19:04 ` Yongseok Koh
2019-04-30 20:46 ` Stephen Hemminger
2019-04-30 20:46   ` Stephen Hemminger
2019-05-01  0:43   ` Yongseok Koh
2019-05-01  0:43     ` Yongseok Koh
2019-05-01  0:56     ` Yongseok Koh
2019-05-01  0:56       ` Yongseok Koh
2019-05-01  1:01 ` [dpdk-dev] [PATCH v2] " Yongseok Koh
2019-05-01  1:01   ` Yongseok Koh
2019-05-01  1:15   ` Yongseok Koh
2019-05-01  1:15     ` Yongseok Koh
2019-05-01  6:10     ` Shahaf Shuler [this message]
2019-05-01  6:10       ` Shahaf Shuler

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=AM0PR0502MB3795C08E031FD749A507D889C33B0@AM0PR0502MB3795.eurprd05.prod.outlook.com \
    --to=shahafs@mellanox.com \
    --cc=dev@dpdk.org \
    --cc=stephen@networkplumber.org \
    --cc=yskoh@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).