DPDK patches and discussions
 help / color / mirror / Atom feed
From: Rahul Lakkireddy <rahul.lakkireddy@chelsio.com>
To: Chas Williams <3chas3@gmail.com>
Cc: "dev@dpdk.org" <dev@dpdk.org>, nirranjan@chelsio.com
Subject: Re: [dpdk-dev] net/cxgbe: DEV_TX_OFFLOAD_MULTI_SEGS support?
Date: Tue, 14 Jan 2020 14:30:40 +0530	[thread overview]
Message-ID: <20200114090039.GA1508@chelsio.com> (raw)
In-Reply-To: <7ba60c65-9448-7885-9932-7258202cef93@gmail.com>

On Monday, January 01/13/20, 2020 at 15:50:21 -0500, Chas Williams wrote:
> 
> It looks like the cxgbe driver doesn't set the DEV_TX_OFFLOAD_MULTI_SEGS
> offload capability. However, it looks like sge.c does have support for
> sending mbuf chains, e.g. write_sgl(). Is this just an oversight or is
> there something fundamentally broken here?

Hi Chas,

Thanks for reporting this. CXGBE does support transmitting mbufs with
multiple segments. However, the corresponding DEV_TX_OFFLOAD_MULTI_SEGS
capability seems to have been missed in the list of supported Tx offload
features. Will send a patch to fix this.

Thanks,
Rahul

      reply	other threads:[~2020-01-14  9:10 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-01-13 20:50 Chas Williams
2020-01-14  9:00 ` Rahul Lakkireddy [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=20200114090039.GA1508@chelsio.com \
    --to=rahul.lakkireddy@chelsio.com \
    --cc=3chas3@gmail.com \
    --cc=dev@dpdk.org \
    --cc=nirranjan@chelsio.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).