public inbox for linux-rdma@vger.kernel.org
 help / color / mirror / Atom feed
From: Jason Gunthorpe <jgg@nvidia.com>
To: Bob Pearson <rpearsonhpe@gmail.com>
Cc: leon@kernel.org, zyjzyj2000@gmail.com,
	linux-rdma@vger.kernel.org, kernel test robot <lkp@intel.com>
Subject: Re: [PATCH for-next v2 00/18] RDMA/rxe: Enable scatter/gather support for skbs
Date: Thu, 24 Nov 2022 15:04:57 -0400	[thread overview]
Message-ID: <Y3/AWaw7a9x7l48B@nvidia.com> (raw)
In-Reply-To: <20221031202403.19062-1-rpearsonhpe@gmail.com>

On Mon, Oct 31, 2022 at 03:23:46PM -0500, Bob Pearson wrote:
> This patch series implements support for network devices that can
> handle or produce fragmented packets. This has the performance
> advantage of reducing the number of copies of payloads for large
> packets.

This doesn't apply, it will need to be rebased/resent

> On the send side packets are created with the network and
> roce headers in the linear portion of the skb and the payload in
> skb fragments. The pad and icrc are appended in an additional fragment
> pointing at data stored in free space in the tail of the linear
> buffer. Only RC messages are supported.
> 
> On the receive side any fragmented skb is supported.
> 
> This patch series is based on the current for-next branch. It also can
> be applied to current for-next after the workqueue patch series is
> applied without change.

The concept seems good

Jason

      reply	other threads:[~2022-11-24 19:05 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-10-31 20:23 [PATCH for-next v2 00/18] RDMA/rxe: Enable scatter/gather support for skbs Bob Pearson
2022-11-24 19:04 ` 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=Y3/AWaw7a9x7l48B@nvidia.com \
    --to=jgg@nvidia.com \
    --cc=leon@kernel.org \
    --cc=linux-rdma@vger.kernel.org \
    --cc=lkp@intel.com \
    --cc=rpearsonhpe@gmail.com \
    --cc=zyjzyj2000@gmail.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