From: "Ouyang, Changchun" <changchun.ouyang@intel.com>
To: "Xie, Huawei" <huawei.xie@intel.com>,
"Czaus, Tomasz" <tomasz.czaus@intel.com>,
"dev@dpdk.org" <dev@dpdk.org>
Subject: Re: [dpdk-dev] One pkt in mbuf chain - virtio pmd driver
Date: Thu, 7 Aug 2014 07:18:21 +0000 [thread overview]
Message-ID: <F52918179C57134FAEC9EA62FA2F962511821140@shsmsx102.ccr.corp.intel.com> (raw)
In-Reply-To: <C37D651A908B024F974696C65296B57B0F25C4F3@SHSMSX101.ccr.corp.intel.com>
It is one feature in developing,
scatter and mergeable RX will be support in virtio subsequent patch.
Thanks
Changchun
> -----Original Message-----
> From: dev [mailto:dev-bounces@dpdk.org] On Behalf Of Xie, Huawei
> Sent: Thursday, August 7, 2014 3:07 PM
> To: Czaus, Tomasz; dev@dpdk.org
> Subject: Re: [dpdk-dev] One pkt in mbuf chain - virtio pmd driver
>
> Hi Tomasz:
> This is a known issue in user space vhost. Will be fixed in subsequent patch
> once the vhost lib is applied.
>
> BR.
> -Huawei
> > -----Original Message-----
> > From: dev [mailto:dev-bounces@dpdk.org] On Behalf Of Czaus, Tomasz
> > Sent: Thursday, August 07, 2014 2:20 PM
> > To: dev@dpdk.org
> > Subject: [dpdk-dev] One pkt in mbuf chain - virtio pmd driver
> >
> > Hello,
> >
> > Does virtio pmd driver support scenario when a frame fits in mbuf
> > chain, this means all headers (eth/ipv4/tcp) are located in first mbuf
> > and user data is located in next mbuf. I have asked the same question
> > on dpdk-ovs mailing group, here is a thread and more details:
> >
> > https://lists.01.org/pipermail/dpdk-ovs/2014-August/001557.html
> >
> > Best Regards,
> > Tomasz Czaus
> >
> > --------------------------------------------------------------------
> >
> > Intel Technology Poland sp. z o.o.
> > ul. Slowackiego 173 | 80-298 Gdansk | Sad Rejonowy Gdansk Polnoc | VII
> > Wydzial Gospodarczy Krajowego Rejestru Sadowego - KRS 101882 | NIP
> > 957-07-
> > 52-316 | Kapital zakladowy 200.000 PLN.
> >
> > Ta wiadomosc wraz z zalacznikami jest przeznaczona dla okreslonego
> > adresata i moze zawierac informacje poufne. W razie przypadkowego
> > otrzymania tej wiadomosci, prosimy o powiadomienie nadawcy oraz trwale
> > jej usuniecie; jakiekolwiek przegladanie lub rozpowszechnianie jest
> > zabronione.
> > This e-mail and any attachments may contain confidential material for
> > the sole use of the intended recipient(s). If you are not the intended
> > recipient, please contact the sender and delete all copies; any review
> > or distribution by others is strictly prohibited.
next prev parent reply other threads:[~2014-08-07 7:17 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-08-07 6:19 Czaus, Tomasz
2014-08-07 7:06 ` Xie, Huawei
2014-08-07 7:18 ` Ouyang, Changchun [this message]
2014-08-08 5:51 ` Czaus, Tomasz
2014-08-07 16:36 ` Stephen Hemminger
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=F52918179C57134FAEC9EA62FA2F962511821140@shsmsx102.ccr.corp.intel.com \
--to=changchun.ouyang@intel.com \
--cc=dev@dpdk.org \
--cc=huawei.xie@intel.com \
--cc=tomasz.czaus@intel.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).