DPDK usage discussions
 help / color / mirror / Atom feed
From: tom.barbette@ulg.ac.be
To: Anupam Kapoor <anupam.kapoor@gmail.com>
Cc: Avi Cohen <avi.cohen@huawei.com>, users@dpdk.org
Subject: Re: [dpdk-users] KNI - mbuf-sk_buff converstion
Date: Wed, 21 Dec 2016 15:01:31 +0100 (CET)	[thread overview]
Message-ID: <1412102721.21124766.1482328891756.JavaMail.zimbra@ulg.ac.be> (raw)
In-Reply-To: <CAEXHiZFdaZpTJJyZ3djXU3r-wMiWdS=WvhfW5qZ-DoUPPf-mJQ@mail.gmail.com>

The memory space could be mapped when converting an mbuf to skbuff (while as you say it would be much harder the other way), but I don't see it done in the KNI code.

It memcpy the whole packet.

Out of curiosity, are there plan on using mapped skbuff?

Tom Barbette 
PhD Student @ Université de Liège 

Office 1/13 
Bâtiment B37 
Quartier Polytech 
Allée de la découverte, 12 
4000 Liège 

04/366 91 75 
0479/60 94 63 


----- Mail original -----
De: "Anupam Kapoor" <anupam.kapoor@gmail.com>
À: "Avi Cohen" <avi.cohen@huawei.com>
Cc: users@dpdk.org
Envoyé: Mercredi 21 Décembre 2016 09:28:46
Objet: Re: [dpdk-users] KNI - mbuf-sk_buff converstion

On Wed, Dec 21, 2016 at 1:09 PM, Avi Cohen <avi.cohen@huawei.com> wrote:

> are zero_copy with respect  to the packet data (headers+payload) - is this
> correc


​umm mbuf's, and skb's are in different address spaces...

--
kind regards
anupam​


In the beginning was the lambda, and the lambda was with Emacs, and Emacs
was the lambda.

      reply	other threads:[~2016-12-21 14:01 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-12-21  7:39 Avi Cohen
2016-12-21  8:28 ` Anupam Kapoor
2016-12-21 14:01   ` tom.barbette [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=1412102721.21124766.1482328891756.JavaMail.zimbra@ulg.ac.be \
    --to=tom.barbette@ulg.ac.be \
    --cc=anupam.kapoor@gmail.com \
    --cc=avi.cohen@huawei.com \
    --cc=users@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).