All of lore.kernel.org
 help / color / mirror / Atom feed
From: Leon Romanovsky <leon@kernel.org>
To: Eric Dumazet <edumazet@google.com>
Cc: "David S . Miller" <davem@davemloft.net>,
	Jakub Kicinski <kuba@kernel.org>, Paolo Abeni <pabeni@redhat.com>,
	Tariq Toukan <tariqt@nvidia.com>, Wei Wang <weiwan@google.com>,
	netdev@vger.kernel.org, eric.dumazet@gmail.com
Subject: Re: [PATCH net-next 0/3] mlx4: better BIG-TCP support
Date: Wed, 7 Dec 2022 09:49:01 +0200	[thread overview]
Message-ID: <Y5BFbc0hhLhTLILF@unreal> (raw)
In-Reply-To: <20221206055059.1877471-1-edumazet@google.com>

On Tue, Dec 06, 2022 at 05:50:56AM +0000, Eric Dumazet wrote:
> mlx4 uses a bounce buffer in TX whenever the tx descriptors
> wrap around the right edge of the ring.
> 
> Size of this bounce buffer was hard coded and can be
> increased if/when needed.
> 
> Eric Dumazet (3):
>   net/mlx4: rename two constants
>   net/mlx4: MLX4_TX_BOUNCE_BUFFER_SIZE depends on MAX_SKB_FRAGS
>   net/mlx4: small optimization in mlx4_en_xmit()
> 
>  drivers/net/ethernet/mellanox/mlx4/en_tx.c   | 18 ++++++++++--------
>  drivers/net/ethernet/mellanox/mlx4/mlx4_en.h | 18 +++++++++++++-----
>  2 files changed, 23 insertions(+), 13 deletions(-)
> 

Thanks,
Reviewed-by: Leon Romanovsky <leonro@nvidia.com>

      parent reply	other threads:[~2022-12-07  7:49 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-12-06  5:50 [PATCH net-next 0/3] mlx4: better BIG-TCP support Eric Dumazet
2022-12-06  5:50 ` [PATCH net-next 1/3] net/mlx4: rename two constants Eric Dumazet
2022-12-06  5:50 ` [PATCH net-next 2/3] net/mlx4: MLX4_TX_BOUNCE_BUFFER_SIZE depends on MAX_SKB_FRAGS Eric Dumazet
2022-12-07 12:40   ` Tariq Toukan
2022-12-07 12:53     ` Eric Dumazet
2022-12-07 13:06       ` Eric Dumazet
2022-12-07 15:14         ` Tariq Toukan
2022-12-07 15:41           ` Eric Dumazet
2022-12-06  5:50 ` [PATCH net-next 3/3] net/mlx4: small optimization in mlx4_en_xmit() Eric Dumazet
2022-12-07  7:49 ` Leon Romanovsky [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=Y5BFbc0hhLhTLILF@unreal \
    --to=leon@kernel.org \
    --cc=davem@davemloft.net \
    --cc=edumazet@google.com \
    --cc=eric.dumazet@gmail.com \
    --cc=kuba@kernel.org \
    --cc=netdev@vger.kernel.org \
    --cc=pabeni@redhat.com \
    --cc=tariqt@nvidia.com \
    --cc=weiwan@google.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.