From: Stephen Hemminger <stephen-OTpzqLSitTUnbdJkjeBofR2eb7JE58TQ@public.gmane.org>
To: "Czaus, Tomasz" <tomasz.czaus-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org>
Cc: "dev-VfR2kkLFssw@public.gmane.org" <dev-VfR2kkLFssw@public.gmane.org>
Subject: Re: One pkt in mbuf chain - virtio pmd driver
Date: Thu, 7 Aug 2014 09:36:51 -0700 [thread overview]
Message-ID: <20140807093651.09d2f483@haswell.linuxnetplumber.net> (raw)
In-Reply-To: <4060631EACBB65409E09BBBDAF62A4C5347B4F29-kPTMFJFq+rELt2AQoY/u9bfspsVTdybXVpNB7YpNyf8@public.gmane.org>
On Thu, 7 Aug 2014 06:19:58 +0000
"Czaus, Tomasz" <tomasz.czaus-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org> wrote:
> 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
Existing DPDK 1.7 virtio driver does not.
I wrote a virtio DPDK driver (before the 1.6 one) that does handle it, so it is possible.
I have some patches to handle multi-part mbuf and messages, based on backport
from that driver but they are untested.
prev parent reply other threads:[~2014-08-07 16:36 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-08-07 6:19 One pkt in mbuf chain - virtio pmd driver Czaus, Tomasz
[not found] ` <4060631EACBB65409E09BBBDAF62A4C5347B4F29-kPTMFJFq+rELt2AQoY/u9bfspsVTdybXVpNB7YpNyf8@public.gmane.org>
2014-08-07 7:06 ` Xie, Huawei
[not found] ` <C37D651A908B024F974696C65296B57B0F25C4F3-0J0gbvR4kThpB2pF5aRoyrfspsVTdybXVpNB7YpNyf8@public.gmane.org>
2014-08-07 7:18 ` Ouyang, Changchun
2014-08-08 5:51 ` Czaus, Tomasz
2014-08-07 16:36 ` Stephen Hemminger [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=20140807093651.09d2f483@haswell.linuxnetplumber.net \
--to=stephen-otpzqlsittunbdjkjebofr2eb7je58tq@public.gmane.org \
--cc=dev-VfR2kkLFssw@public.gmane.org \
--cc=tomasz.czaus-ral2JQCrhuEAvxtiuMwx3w@public.gmane.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).