From: Alex Markuze <alex@weka.io>
To: "Ananyev, Konstantin" <konstantin.ananyev@intel.com>
Cc: "dev@dpdk.org" <dev@dpdk.org>
Subject: Re: [dpdk-dev] Aligned RX data.
Date: Mon, 13 Oct 2014 11:47:24 +0300 [thread overview]
Message-ID: <CAKfHP0XMYEGTjvyTcs5MAkLiW0Rvic+sn2oqNfHFnz=13b44VA@mail.gmail.com> (raw)
In-Reply-To: <CAKfHP0VRSzo8YtN4aziEBLCvQ3icqe=ovxD-BZBx_Y2K4751Eg@mail.gmail.com>
Hi All,
Is there a way to create a mempool such that all mbufs are aligned to X.
lets say X is 512.
Thanks.
On Sat, Oct 11, 2014 at 5:04 PM, Alex Markuze <alex@weka.io> wrote:
> O.k, And how would I do that?
> I'm guessing there is something I can control in rte_pktmbuf_pool_init?
> I would appreciate If you could spare a word or two in the matter.
>
> On Tue, Oct 7, 2014 at 7:11 PM, Ananyev, Konstantin <
> konstantin.ananyev@intel.com> wrote:
>
>>
>>
>> > -----Original Message-----
>> > From: Ananyev, Konstantin
>> > Sent: Tuesday, October 07, 2014 5:03 PM
>> > To: Ananyev, Konstantin
>> > Subject: FW: [dpdk-dev] Aligned RX data.
>> >
>> >
>> >
>> > From: Alex Markuze [mailto:alex@weka.io]
>> > Sent: Tuesday, October 07, 2014 4:52 PM
>> > To: Ananyev, Konstantin
>> > Cc: dev@dpdk.org
>> > Subject: Re: [dpdk-dev] Aligned RX data.
>> >
>> > RTE_PKTMBUF_HEADROOM defines the headroom
>>
>> Yes.
>>
>> >this would be true only if the buff_start was aligned to 512 which is
>> not.
>>
>> As I said: " Make sure that your all your mbufs are aligned by 512".
>>
>> Konstantin
>>
>> >
>> > On Tue, Oct 7, 2014 at 1:05 PM, Ananyev, Konstantin <
>> konstantin.ananyev@intel.com> wrote:
>> >
>> >
>> > > -----Original Message-----
>> > > From: dev [mailto:dev-bounces@dpdk.org] On Behalf Of Alex Markuze
>> > > Sent: Tuesday, October 07, 2014 10:40 AM
>> > > To: dev@dpdk.org
>> > > Subject: [dpdk-dev] Aligned RX data.
>> > >
>> > > Hi , I'm trying to receive aligned packets from the wire.
>> > > Meaning that for all received packets the pkt.data is always aligned
>> to
>> > > (512 -H).
>> > >
>> > > Looking at the pmds of ixgbe/vmxnet I see that the pmds call
>> > > __rte_mbuf_raw_alloc and set the rx descriptor with a
>> > > RTE_MBUF_DATA_DMA_ADDR_DEFAULT
>> > > Instead of the more appropriate RTE_MBUF_DATA_DMA_ADDR.
>> > >
>> > > Do I need to modify each pmd I'm using to be able to receive aligned
>> data?
>> > Make sure that your all your mbufs are aligned by 512 and set in your
>> config RTE_PKTMBUF_HEADROOM=512-H?
>> >
>> >
>> > > Or have I missed something?
>> > >
>> > > Thanks
>>
>>
>
next prev parent reply other threads:[~2014-10-13 8:39 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-10-07 9:40 Alex Markuze
2014-10-07 10:05 ` Ananyev, Konstantin
2014-10-07 15:51 ` Alex Markuze
[not found] ` <2601191342CEEE43887BDE71AB9772582139126C@IRSMSX105.ger.corp.intel.com>
2014-10-07 16:11 ` Ananyev, Konstantin
2014-10-11 14:04 ` Alex Markuze
2014-10-13 8:47 ` Alex Markuze [this message]
[not found] ` <2601191342CEEE43887BDE71AB9772582139336F@IRSMSX105.ger.corp.intel.com>
2014-10-13 11:43 ` Ananyev, Konstantin
2014-10-13 15:20 ` Alex Markuze
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='CAKfHP0XMYEGTjvyTcs5MAkLiW0Rvic+sn2oqNfHFnz=13b44VA@mail.gmail.com' \
--to=alex@weka.io \
--cc=dev@dpdk.org \
--cc=konstantin.ananyev@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).