> > Bug: when "core id" is greater than 9, the cpu_layout.py output doesn't
> > align.>
> > Socket 0Socket 1
> > - -
> >
> > Core 9 [4, 16] [10, 22]
> >
> > Core 10 [5, 17] [11, 23]
> >
> > Solution: adjust output format to
2014-06-18 21:33, Bruce Richardson:
> When testing compilation on BSD systems and with the clang compiler a
> number of minor issues were encountered. This patchset fixes some of these.
Acked-by: Thomas Monjalon
Applied for version 1.7.0.
Thanks
--
Thomas
> Simplifiy the logic in the error checking branch. Rather than having a
> single error branch which checked both RX and TX conditions and made
> extensive use of the ? operator, move the error checking explicitly into
> the RX and TX individual branches.
>
> The original code caused compilation i
> > This patchset fixes an issue with VFIO where DPDK initialization could
> > fail even if the user didn't want to use VFIO in the first place. Also,
> > more verbose and descriptive error messages were added to VFIO code, for
> > example distinguishing between a failed ioctl() call and an unsuppo
-Original Message-
From: Thomas Monjalon [mailto:thomas.monja...@6wind.com]
Sent: Wednesday, June 18, 2014 5:24 PM
To: Zhang, Helin
Cc: Chen, Jing D; dev at dpdk.org
Subject: Re: [dpdk-dev] [PATCH v2 00/27] Add i40e PMD support
2014-06-18 08:51, Zhang, Helin:
> Thomas Monjalon:
> > Some
2014-06-17 19:42, Bruce Richardson:
> Mark the rte_log, cmdline_printf and rte_snprintf functions as
> being printf-style functions. This causes compilation errors
> due to mis-matched parameter types, so the parameter types are
> fixed where appropriate.
>
> Signed-off-by: Bruce Richardson
Nice
> -Original Message-
> From: dev [mailto:dev-bounces at dpdk.org] On Behalf Of Stephen Hemminger
> Sent: Wednesday, June 18, 2014 12:36 AM
> To: Stephen Hemminger
> Cc: dev at dpdk.org
> Subject: Re: [dpdk-dev] [PATCH 0/8] virtio driver phase 2
>
> On Fri, 13 Jun 2014 18:06:17 -0700
> Ste
2014-06-17 19:11, Palin, Francois:
> Just checking once more on a question I have asked back in January:
>
> We would like to know if DPDK support for the i217 will be provided anytime
> soon.
> The Supported NICs list doesn't show the i217. Intel DPDK Release Notes
> don't mention the i217 either
Thanks,
it has the same effect as my changeee
i found the lost packets issue... it was related to my app implementation
(a bug with increasing the number of segments at the nb_segs variable).
anyway thanks.
On Wed, Jun 11, 2014 at 7:18 PM, Thomas Monjalon
wrote:
> 2014-05-30 15:44, Helmut Si
2014-06-11 21:43, Helin Zhang:
> -#if !(RHEL_RELEASE_CODE && RHEL_RELEASE_CODE >= RHEL_RELEASE_VERSION(6,4))
> -static inline bool ether_addr_equal(const u8 *addr1, const u8 *addr2)
> +static inline bool __kc_ether_addr_equal(const u8 *addr1, const u8 *addr2)
> {
> return !compare_ether_addr
From: Pablo de Lara
When parsing EAL option --base-virtaddr
errno was not being set to 0 before calling strtoull,
therefore function might fail unnecesarily.
Signed-off-by: Pablo de Lara
---
lib/librte_eal/linuxapp/eal/eal.c |1 +
1 files changed, 1 insertions(+), 0 deletions(-)
diff --gi
Must reset errno to zero before calling strtoull(), else on success it
could be any arbitrary value from past errors.
Signed-off-by: Aaron Campbell
---
lib/librte_eal/linuxapp/eal/eal.c | 1 +
1 file changed, 1 insertion(+)
diff --git a/lib/librte_eal/linuxapp/eal/eal.c
b/lib/librte_eal/linuxa
Hi Aaron,
It seems that Pablo De Lara has beat you to it by a few minutes :-) Are there
any other places this could potentially happen?
> Must reset errno to zero before calling strtoull(), else on success it could
> be
> any arbitrary value from past errors.
>
> Signed-off-by: Aaron Campbell
Yes, that was extremely bizarre. I didn?t check the whole project, but at
least eal_parse_socket_mem() in the same file was already correct. Pablo you
can add me to Acked-by, obviously. :-)
-Aaron
On Jun 19, 2014, at 12:46 PM, Burakov, Anatoly
wrote:
> Hi Aaron,
>
> It seems that Pablo De
> -Original Message-
> From: dev [mailto:dev-bounces at dpdk.org] On Behalf Of Pablo de Lara
> Sent: Thursday, June 19, 2014 4:35 PM
> To: dev at dpdk.org
> Subject: [dpdk-dev] [PATCH] eal: Fixed EAL option --base-virtaddr
>
> From: Pablo de Lara
>
> When parsing EAL option --base-virtad
> > When parsing EAL option --base-virtaddr
> > errno was not being set to 0 before calling strtoull, therefore function
> > might fail unnecesarily.
> >
> > Signed-off-by: Pablo de Lara
>
> Acked-by: Anatoly Burakov
Signed-off-by: Aaron Campbell
Whaoh! We received same patch from 2 guys in f
Mark the rte_log, cmdline_printf and rte_snprintf functions as
being printf-style functions. This causes compilation errors
due to mis-matched parameter types, so the parameter types are
fixed where appropriate.
Changes in V2:
* Additional fixes for ivshmem-target compilation
Signed-off-by: Bruce
Take the existing get_pkt API and split out the parts for requesting a new
packet from the part to poll for arrival of a new packet. These individual
functions can then be used independently of the get function, which still acts
as before.
The split functions for request and poll will allow a work
Only some devices support the link state interrupt configuration option.
Link state control does not work in virtual drivers
(virtio, vmxnet3, igbvf, and ixgbevf). Instead of having the application
try and guess whether it will work or not provide a driver flag that
can be checked instead.
Note: i
19 matches
Mail list logo
