From: "Richardson, Bruce" <bruce.richardson@intel.com>
To: sabu kurian <sabu2kurian@gmail.com>
Cc: "dev@dpdk.org" <dev@dpdk.org>
Subject: Re: [dpdk-dev] Packet crafting....
Date: Fri, 14 Mar 2014 11:49:16 +0000 [thread overview]
Message-ID: <59AF69C657FD0841A61C55336867B5B01A9C4588@IRSMSX103.ger.corp.intel.com> (raw)
In-Reply-To: <CAJ2bnfBgJiGQ+VumJY6f6R8ecmvEnQ4D24TyiXWmBwQxR6jZJg@mail.gmail.com>
> From: sabu kurian [mailto:sabu2kurian@gmail.com]
> Sent: Friday, March 14, 2014 11:38 AM
> To: Richardson, Bruce
> Cc: dev@dpdk.org
> Subject: Re: [dpdk-dev] Packet crafting....
>
> Thanks on the reply Richardson. You did mention something like "Don't forget that when you get the mbuf from
> rte_pktmbuf_alloc, you also need to set the length value to the appropriate size." .
>
> Like I'm allocating the mbuf using rte_mbuf . The rte_mempool_create has already set the maximum packet size
> for a mbuf and the number of mbuf's and all. So do I really need to use rte_pktmbuf_alloc ?
How are you getting an mbuf from the pool, if not using rte_pktmbuf_alloc?
When you have an mbuf, that buffer has a maximum size, generally around 2k. However, the packet inside that buffer is generally smaller than the overall buffer size and you must configure that size, otherwise the PMD, and therefore the NIC, has no idea how much data out of that 2k buffer needs to be transmitted.
next prev parent reply other threads:[~2014-03-14 11:47 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-03-14 9:31 sabu kurian
2014-03-14 9:57 ` Richardson, Bruce
2014-03-14 10:09 ` sabu kurian
2014-03-14 11:08 ` Richardson, Bruce
2014-03-14 11:38 ` sabu kurian
2014-03-14 11:49 ` Richardson, Bruce [this message]
2014-03-14 12:04 ` sabu kurian
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=59AF69C657FD0841A61C55336867B5B01A9C4588@IRSMSX103.ger.corp.intel.com \
--to=bruce.richardson@intel.com \
--cc=dev@dpdk.org \
--cc=sabu2kurian@gmail.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).