DPDK patches and discussions
 help / color / mirror / Atom feed
From: Rajasekhar Pulluru <pullururajasekhar@gmail.com>
To: dev@dpdk.org
Subject: [dpdk-dev] Queries on dpdk buffer allocation and kni
Date: Tue, 31 Mar 2015 20:43:19 +0530	[thread overview]
Message-ID: <CAGA5_H7vifeV=8Rtvd8M0VPWzz70xQPcZ8v4ND7+GG=15-_qkw@mail.gmail.com> (raw)

Dear Group members,

I have been trying to understand the dpdk code and have got two queries.

1. descriptor rings and packet buffer allocation

Looking at the linux native e1000 kernel driver,
Memory for NIC's tx and rx descriptor rings are allocated using
dma_alloc_coherent.
Memory for rx packet buffers are allocated using netdev_alloc_skb and
dma address (after dma_map_single) of skb->data is set to rx
descriptor to receive packet onto skb.

Looking at dpdk user space driver, all rings and packet allocation is
done using (dpdk) mem pools.

I would like to know

a) whether the mem pool internally uses dma_alloc_coherent like apis
to allocate buffers
b) if the buffer is allocated by kernel, how does the user space
application map them and access the packet data directly.

2. kni

what is the internal mechanism used to implement FIFO-based shared
memory (used between kernel and user-land).

Thanks in advance,
Rajasekhar

                 reply	other threads:[~2015-03-31 15:13 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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='CAGA5_H7vifeV=8Rtvd8M0VPWzz70xQPcZ8v4ND7+GG=15-_qkw@mail.gmail.com' \
    --to=pullururajasekhar@gmail.com \
    --cc=dev@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).