From: Kevin Traynor <ktraynor@redhat.com>
To: David Marchand <david.marchand@redhat.com>, stable@dpdk.org
Subject: Re: [dpdk-stable] [PATCH 18.11] net/pcap: fix concurrent multiseg Tx
Date: Thu, 5 Sep 2019 17:08:47 +0100 [thread overview]
Message-ID: <b6effbd1-2b2d-d735-ba45-ec9c29f7f5c5@redhat.com> (raw)
In-Reply-To: <1567683366-6140-1-git-send-email-david.marchand@redhat.com>
On 05/09/2019 12:36, David Marchand wrote:
> [ upstream commit fbbbf553f268b94d6dbe491a31d1f0c8d227465f ]
>
> Two cores can send multi segment packets on two different pcap ports.
> Because of this, we can't have one single buffer to linearize packets.
>
> Use rte_pktmbuf_read() to copy the packet into a buffer on the stack
> and remove eth_pcap_gather_data() when necessary (if the mbuf is
> contiguous, rte_pktmbuf_read() just points at the buffer address).
>
> Fixes: 6db141c91e1f ("pcap: support jumbo frames")
>
> Signed-off-by: David Marchand <david.marchand@redhat.com>
> Acked-by: Ferruh Yigit <ferruh.yigit@intel.com>
Thanks David, added into the queue for push to stable branch next week.
Kevin.
prev parent reply other threads:[~2019-09-05 16:08 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-09-05 11:36 David Marchand
2019-09-05 16:08 ` Kevin Traynor [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=b6effbd1-2b2d-d735-ba45-ec9c29f7f5c5@redhat.com \
--to=ktraynor@redhat.com \
--cc=david.marchand@redhat.com \
--cc=stable@dpdk.org \
/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).