One caveat - a compiler_barrier should be enough when both sides are using
strongly-ordered memory operations (as in the case of the rings). Weakly
ordered operations will still need fencing.
-Venky
-Original Message-
From: dev [mailto:dev-boun...@dpdk.org] On Behalf Of Stephen Hemminge
Hi Stephen,
On 03/27/2014 08:06 PM, Stephen Hemminger wrote:
> Long answer: for the multple CPU access ring, it is equivalent to smp_wmb and
> smp_rmb
> in Linux kernel. For x86 where DPDK is used, this can normally be replaced
> by simpler
> compiler barrier. In kernel there is a special fl
Hi folks,
Just to clarify, the purpose of hw.nic_uio.bdfs is to remove NICs from drivers
not owned by nic_uio and add them to a pool of unbound devices.
As with the Linux equivalent driver(igb_uio), nic_uio will then attempt to bind
any unbound NICs and make them available for DPDK.
However, th
dunload nic_uio
[oki@ ~]$ pciconf -l | egrep '(em|uio)'
em0 at pci0:2:1:0: class=0x02 card=0x075015ad chip=0x100f8086 rev=0x01
hdr=0x00
[oki@ ~]$
2014-03-26 14:35 GMT+09:00 Fred Pedrisa :
Hi, guys.
This variable is not working as intended for FreeBSD :(
It does not dettach nic_uio from the wanted ports :/
-- next part --
An embedded and charset-unspecified text was scrubbed...
Name: nic_uio.c
URL:
<http://dpdk.org/ml/archives/dev/attachments/20140327/f6c5c64a/attachment.c>
Hi,
I have a question about a vhost sample application.
According to the documentation, it seems the application should run on
2MB huge pages.
What is a reason the application can't support 1GB huge page?
Thanks,
Tetsuya Mukawa
Hi,
The commit 286bd05bf7 [1] removed the memory barriers in the ring
functions. This patch is present in DPDK since version 1.4.0r0, so I
guess it does not cause any issue.
But after checking the excellent Linux kernel documentation about memory
barriers [2], I'm wondering why memory barriers wo
Hello,
It just requires a small code change :), and it can work in the expected
way.
So you mean bdfs is to 'select' the only wanted devices yes ? May I change
my code proposition for you ?
Sincerely,
Fred Pedrisa
-Mensagem original-
De: Carew, Alan [mailto:alan.carew at intel.com]
En
On Thu, 27 Mar 2014 20:47:37 +0100
Olivier MATZ wrote:
> Hi Stephen,
>
> On 03/27/2014 08:06 PM, Stephen Hemminger wrote:
> > Long answer: for the multple CPU access ring, it is equivalent to smp_wmb
> > and smp_rmb
> > in Linux kernel. For x86 where DPDK is used, this can normally be
> > re
On Thu, 27 Mar 2014 17:48:21 +0100
Olivier MATZ wrote:
> Hi,
>
> The commit 286bd05bf7 [1] removed the memory barriers in the ring
> functions. This patch is present in DPDK since version 1.4.0r0, so I
> guess it does not cause any issue.
>
> But after checking the excellent Linux kernel docume
> > Signed-off-by: Thomas Monjalon
>
> Reviewed-by: Olivier Matz
Applied
--
Thomas
> > Signed-off-by: Thomas Monjalon
>
> Reviewed-by: Olivier Matz
Applied
--
Thomas
> > MEMNIC doc may be installed with other DPDK docs.
> > So more descriptive naming is required.
> >
> > A rule is created in order to have the same rule style for lib and doc.
> >
> > Signed-off-by: Thomas Monjalon
>
> [...]
>
> > +$(DESTDIR)$(docdir)/$(DOC) : $S/README.rst
> > + install
there is problem in l2fwd_send_packet().
l2fwd and some other examples assume burst traffic.
l2fwd doesn't send packet if qconf->tx_mbufs[port].len < MAX_PKT_BURST.
2014-03-27 9:56 GMT+09:00 Fred Pedrisa :
> It is just a ping test, from one PC to another, using 2 ports as a L2
> Bridge.
>
> 64
2014-03-26 17:48, Olivier MATZ:
> Hi Hiroshi-san,
>
> On 03/11/2014 06:40 AM, Hiroshi Shimamoto wrote:
> > From: Hiroshi Shimamoto
> >
> > The current MEMNIC PMD cannot handle multiple segments.
> >
> > Add the functionality to transmit a mbuf which has multiple segments.
> > Walk every segment
Hello,
Im my first attempt, I had to restart the server :D
-Mensagem original-
De: dev [mailto:dev-bounces at dpdk.org] Em nome de Randall Stewart
Enviada em: quinta-feira, 27 de mar?o de 2014 08:26
Para: dev at dpdk.org
Assunto: Re: [dpdk-dev] Attempting to get the DPDK to build for Free
> > Signed-off-by: Thomas Monjalon
>
> Reviewed-by: Olivier Matz
Applied, thanks
--
Thomas
> > S specify source directory (when not already in).
> > O specify output directory (when different of current one).
> >
> > Signed-off-by: Thomas Monjalon
>
> Reviewed-by: Olivier Matz
Applied, thanks
--
Thomas
> > Fix help.
> > Also define CC and remove RTE_CONFIG variable.
> >
> > Signed-off-by: Thomas Monjalon
>
> Reviewed-by: Olivier Matz
Applied, thanks
--
Thomas
> > A typo was found by gcc-4.8:
> > virtio_user.c:744:15: error: argument to 'sizeof' in 'memset' call is the
> > same expression as the destination; did you mean to dereference it?
> > [-Werror=sizeof-pointer-memaccess]
> >
> > sizeof(tq->tx_hdrs[sz - 1].header));
> >
> >
On 02/04/2014 04:54 PM, Thomas Monjalon wrote:
> Signed-off-by: Thomas Monjalon
> ---
> pmd/Makefile |7 ++-
> 1 file changed, 2 insertions(+), 5 deletions(-)
>
> diff --git a/pmd/Makefile b/pmd/Makefile
> index 730b126..5edc44e 100644
> --- a/pmd/Makefile
> +++ b/pmd/Makefile
> @@ -29,
On 02/04/2014 04:54 PM, Thomas Monjalon wrote:
> Signed-off-by: Thomas Monjalon
> ---
> pmd/Makefile |2 ++
> 1 file changed, 2 insertions(+)
>
> diff --git a/pmd/Makefile b/pmd/Makefile
> index 1e24a15..730b126 100644
> --- a/pmd/Makefile
> +++ b/pmd/Makefile
> @@ -79,6 +79,8 @@ endif
>
Hi Thomas,
On 02/04/2014 04:54 PM, Thomas Monjalon wrote:
> MEMNIC doc may be installed with other DPDK docs.
> So more descriptive naming is required.
>
> A rule is created in order to have the same rule style for lib and doc.
>
> Signed-off-by: Thomas Monjalon
> ---
> pmd/Makefile |9 +
On 02/04/2014 04:54 PM, Thomas Monjalon wrote:
> Signed-off-by: Thomas Monjalon
Reviewed-by: Olivier Matz
On 02/04/2014 04:54 PM, Thomas Monjalon wrote:
> S specify source directory (when not already in).
> O specify output directory (when different of current one).
>
> Signed-off-by: Thomas Monjalon
Reviewed-by: Olivier Matz
On 02/04/2014 04:54 PM, Thomas Monjalon wrote:
> Fix help.
> Also define CC and remove RTE_CONFIG variable.
>
> Signed-off-by: Thomas Monjalon
Reviewed-by: Olivier Matz
Hello Thomas,
On 02/04/2014 04:54 PM, Thomas Monjalon wrote:
> A typo was found by gcc-4.8:
> virtio_user.c:744:15: error: argument to 'sizeof' in 'memset' call is the
> same expression as the destination; did you mean to dereference it?
> [-Werror=sizeof-pointer-memaccess]
> sizeof(tq->
Ok
I have figured this one out ;-)
When you do
kldload ./contigmem.ko
It trys to malloc up a chunk of memory (1Gig it looks by default).. and if
a contiguious piece of memory is not available.. it fails.. which causes
the failure back to kldload that says ?Exec format error?.
Not very descript
>
> Hi all:
>
> I have a stock 9.2Release FreeBSD system and am attempting to build the DPDK
> for it. I have
> followed the steps i.e:
>
> 1) Gotten the ports in:
> - dialog4ports
> - gcc 4.8
> - gmake
> - coreutils
> - libexecinfo
>
> 2) Ran the make
> - gmake install T=x86_64-defaul
Hello,
I've solved the problem.
It was related with the threshoulds of the network card, that must be
adjusted following the manual as explained inside the example code.
It is not related with the maximum burst :)
So now all fine !
-Mensagem original-
De: dev [mailto:dev-bounces at dpd
29 matches
Mail list logo
