DPDK usage discussions
 help / color / mirror / Atom feed
From: Sergey Matov <smatov@mirantis.com>
To: Rajaraman Balasubramanian <rajaramanb20@gmail.com>
Cc: users@dpdk.org
Subject: Re: [dpdk-users] Fwd: FW: DPDK Compilation Error
Date: Wed, 28 Oct 2015 10:05:28 +0300	[thread overview]
Message-ID: <CAPykWKE-srge6pnxBQ82WLnyLrx6R17CNsW_9Gt3_A1N6AAUUQ@mail.gmail.com> (raw)
In-Reply-To: <CANp2bXbngohx76mA=NRcEOs9UHsm1y0n4LtX7fHtnZxBOJGpog@mail.gmail.com>

Hello Rajaraman.

Currently I've no experience running DPDK on 32 bit machines.
However all recommendation I could give to you is to check out related
problems, such as http://dpdk.org/ml/archives/dev/2014-August/004695.html
AFAIC it seems that using sse version 3 is kind of hard requirement for
configuration you want to compile.

2015-10-28 3:18 GMT+03:00 Rajaraman Balasubramanian <rajaramanb20@gmail.com>
:

> Hi Sergey,
>
>     Thanks for your reply. In my small lab, I don't have SSE3 based CPU. I
> have only SSE2 based CPU.
>
>      I just want to know whether it is mentioned somewhere in the dpdk
> website for 32 bit machines ??
>
>      Also, how can i do it in SSE2 based CPU ??
>
> Thanks,
> Rajaram.
>
> On Mon, Oct 26, 2015 at 7:16 PM, Sergey Matov <smatov@mirantis.com> wrote:
>>
>>> Hello.
>>>
>>> Try to build on platform supported  *Streaming SIMD Extensions 3 (sse3)*
>>> see
>>> #egrep 'sse' /proc/cpuinfo
>>> to make sure your CPU support this instructions
>>>
>>> 2015-10-26 16:03 GMT+03:00 Rajaraman Balasubramanian <
>>> rajaramanb20@gmail.com>:
>>>
>>>> Hi,
>>>>
>>>>     I am getting following compile time error. Herewith attaching
>>>> build.log
>>>> file for your debugging.
>>>>
>>>>
>>>> /home/rajabala/ipaugenblick/ipaugenblick-master/dpdk-2.1.0/i686-native-linuxapp-gcc/include/rte_memcpy.h:625:2:
>>>> error: incompatible type for argument 2 of ‘_mm_storeu_si128’
>>>>   MOVEUNALIGNED_LEFT47(dst, src, n, srcofs);
>>>>
>>>> dpdk-2.1.0/lib/librte_eal/linuxapp/eal/eal_pci.c:39:
>>>> /usr/lib/gcc/i686-linux-gnu/4.8/include/emmintrin.h:700:1: note:
>>>> expected
>>>> ‘__m128i’ but argument is of type ‘int’
>>>>  _mm_storeu_si128 (__m128i *__P, __m128i __B)
>>>>
>>>> I have following configuration details.
>>>>
>>>> GCC - 4.8.2
>>>> GLIBC - 2.19
>>>> TARGET- i686-native-linuxapp-gcc
>>>>
>>>> rajabala@rajabala-desktop:/usr$ cat /proc/cpuinfo
>>>> processor    : 0
>>>> vendor_id    : GenuineIntel
>>>> cpu family    : 15
>>>> model        : 2
>>>> model name    : Intel(R) Pentium(R) 4 CPU 2.00GHz
>>>> stepping    : 4
>>>> microcode    : 0x1e
>>>> cpu MHz        : 2000.227
>>>> cache size    : 512 KB
>>>> physical id    : 0
>>>> siblings    : 1
>>>> core id        : 0
>>>> cpu cores    : 1
>>>> apicid        : 0
>>>> initial apicid    : 0
>>>> fdiv_bug    : no
>>>> f00f_bug    : no
>>>> coma_bug    : no
>>>> fpu        : yes
>>>> fpu_exception    : yes
>>>> cpuid level    : 2
>>>> wp        : yes
>>>> flags        : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca
>>>> cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pebs bts
>>>> bogomips    : 4000.45
>>>> clflush size    : 64
>>>> cache_alignment    : 128
>>>> address sizes    : 36 bits physical, 32 bits virtual
>>>> power management:
>>>>
>>>> rajabala@rajabala-desktop:/usr$
>>>>
>>>>
>>>> rajabala@rajabala-desktop:/usr$ cat /proc/meminfo
>>>> MemTotal:        2963304 kB
>>>> MemFree:         1501568 kB
>>>> Buffers:          211472 kB
>>>> Cached:           668608 kB
>>>> SwapCached:            0 kB
>>>> Active:           687632 kB
>>>> Inactive:         689756 kB
>>>> Active(anon):     498104 kB
>>>> Inactive(anon):   143004 kB
>>>> Active(file):     189528 kB
>>>> Inactive(file):   546752 kB
>>>> Unevictable:          32 kB
>>>> Mlocked:              32 kB
>>>> HighTotal:       2224072 kB
>>>> HighFree:        1257848 kB
>>>> LowTotal:         739232 kB
>>>> LowFree:          243720 kB
>>>> SwapTotal:       2086904 kB
>>>> SwapFree:        2086904 kB
>>>> Dirty:                96 kB
>>>> Writeback:             0 kB
>>>> AnonPages:        497336 kB
>>>> Mapped:           118800 kB
>>>> Shmem:            143804 kB
>>>> Slab:              55168 kB
>>>> SReclaimable:      41316 kB
>>>> SUnreclaim:        13852 kB
>>>> KernelStack:        3440 kB
>>>> PageTables:         7400 kB
>>>> NFS_Unstable:          0 kB
>>>> Bounce:                0 kB
>>>> WritebackTmp:          0 kB
>>>> CommitLimit:     3568556 kB
>>>> Committed_AS:    3128368 kB
>>>> VmallocTotal:     122880 kB
>>>> VmallocUsed:        9404 kB
>>>> VmallocChunk:     110416 kB
>>>> HardwareCorrupted:     0 kB
>>>> AnonHugePages:    157696 kB
>>>> HugePages_Total:       0
>>>> HugePages_Free:        0
>>>> HugePages_Rsvd:        0
>>>> HugePages_Surp:        0
>>>> Hugepagesize:       2048 kB
>>>> DirectMap4k:       18424 kB
>>>> DirectMap2M:      894976 kB
>>>> rajabala@rajabala-desktop:/usr$
>>>>
>>>>
>>>> rajabala@rajabala-desktop:/usr$ gcc -dM -E -march=native - < /dev/null
>>>> |
>>>> grep SSE
>>>> #define __SSE2__ 1
>>>> #define __SSE__ 1
>>>> rajabala@rajabala-desktop:/usr$
>>>>
>>>>
>>>> rajabala@rajabala-desktop:/usr$ gcc -dM -E -march=native - < /dev/null
>>>> |
>>>> grep GNU
>>>> #define __GNUC_PATCHLEVEL__ 2
>>>> #define __GNUC__ 4
>>>> #define __GNUC_MINOR__ 8
>>>> #define __GNUC_GNU_INLINE__ 1
>>>> rajabala@rajabala-desktop:/usr$
>>>>
>>>>
>>>> rajabala@rajabala-desktop:/usr$ uname -a
>>>> Linux rajabala-desktop 3.13.0-53-generic #89-Ubuntu SMP Wed May 20
>>>> 10:34:28
>>>> UTC 2015 i686 i686 i686 GNU/Linux
>>>> rajabala@rajabala-desktop:/usr$
>>>>
>>>>
>>>> rajabala@rajabala-desktop:/usr$ gcc -dM -E -march=native - < /dev/null
>>>> |
>>>> grep linux
>>>> #define __linux 1
>>>> #define __linux__ 1
>>>> #define __gnu_linux__ 1
>>>> #define linux 1
>>>> rajabala@rajabala-desktop:/usr$
>>>>
>>>> rajabala@rajabala-desktop:/usr$ swapon -s
>>>> Filename                Type        Size    Used    Priority
>>>> /dev/sda5                               partition    1038332    0    -1
>>>> /swapfile1                              file        1048572    0    -2
>>>> rajabala@rajabala-desktop:/usr$
>>>> rajabala@rajabala-desktop:/usr$
>>>> rajabala@rajabala-desktop:/usr$ free -m
>>>>              total       used       free     shared    buffers
>>>>  cached
>>>> Mem:          2893       1436       1457        138        206
>>>> 651
>>>> -/+ buffers/cache:        578       2315
>>>> Swap:         2037          0       2037
>>>> rajabala@rajabala-desktop:/usr$
>>>>
>>>>
>>>> if you need more info, please ping me so that I can send you quickly. I
>>>> tried mutiple ways to resolve this issue, but i could not resolve it.
>>>>
>>>> Please tell me how to resolve this issue.
>>>>
>>>> Thanks,
>>>> Rajaram.
>>>>
>>>


-- 
*Best Regards*
*Sergey Matov*
*Mirantis Inc*

      reply	other threads:[~2015-10-28  7:05 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <BLU172-W298EF2026A5F942A009148C4250@phx.gbl>
     [not found] ` <BLU172-W350CB1092C1AA5E427517CC4230@phx.gbl>
2015-10-26 13:03   ` Rajaraman Balasubramanian
     [not found]     ` <CAPykWKGhCnEOyofV-gB5wANJbqRzvzwQ2FEy54RwNar1_Lzv3Q@mail.gmail.com>
     [not found]       ` <CANp2bXb=eeFT8u2Xwapx7MgG75vbcf9QkOuwHLpGRV-EpuC1wg@mail.gmail.com>
2015-10-28  0:18         ` Rajaraman Balasubramanian
2015-10-28  7:05           ` Sergey Matov [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=CAPykWKE-srge6pnxBQ82WLnyLrx6R17CNsW_9Gt3_A1N6AAUUQ@mail.gmail.com \
    --to=smatov@mirantis.com \
    --cc=rajaramanb20@gmail.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).