Thanks a million Maxim! Patch submitted.
On Tue, 2017-02-28 at 18:57 +0300, Maxim Uvarov wrote:
> git format-patch HEAD^
> perl ./scripts/checkpatch.pl *.patch
> > git send-email --to lng-odp@lists.linaro.org *.patc
>
> > On 28 February 2017 at 18:54, Marco Varlese wrote:
> > Hi,
> > I'm trying
git format-patch HEAD^
perl ./scripts/checkpatch.pl *.patch
git send-email --to lng-odp@lists.linaro.org *.patc
On 28 February 2017 at 18:54, Marco Varlese wrote:
> Hi,
> I'm trying to submit the patch but without much success...
>
> mvarlese@linux-yk3w:~/repos> git clone https://git.linaro.org/
Hi,
I'm trying to submit the patch but without much success...
mvarlese@linux-yk3w:~/repos> git clone https://git.linaro.org/lng/odp.git
mvarlese@linux-yk3w:~/repos/odp> git config --global user.name "Marco Varlese"
mvarlese@linux-yk3w:~/repos/odp> git config --global user.email "marco.varlese@s
I've added this topic to the agenda for today's ODP public call. Marco, if
you're able to join us to provide your input to the discussion please do
so. The call is at 15:00 UTC. To join just go to
http://meetings.opendataplane.org. We use the BlueJeans conferencing
system. Thanks.
On Tue, Feb 28,
the problem is that if you compile binary on let's say ubuntu it might not
work on suse with more then 1024 cpus.
On 28 February 2017 at 11:52, Marco Varlese wrote:
> On Tue, 2017-02-28 at 08:12 +, Savolainen, Petri (Nokia - FI/Espoo)
> wrote:
>
> [nip]
>
> > /**
> > * @def ODP_CPUMASK_SIZE
On Tue, 2017-02-28 at 08:12 +, Savolainen, Petri (Nokia - FI/Espoo) wrote:
[nip]
> /**
> * @def ODP_CPUMASK_SIZE
> * Maximum cpumask size, this definition limits the number of individual CPUs
> * that can be accessed in this system.
> */
>
> It cannot be removed, it's part of API. Just n
> -Original Message-
> From: lng-odp [mailto:lng-odp-boun...@lists.linaro.org] On Behalf Of Maxim
> Uvarov
> Sent: Monday, February 27, 2017 6:09 PM
> To: Marco Varlese ; lng-odp@lists.linaro.org
> Subject: Re: [lng-odp] Compilation error of ODP on Linux x86_64 platfor
On 02/27/17 19:05, Marco Varlese wrote:
> On Mon, 2017-02-27 at 18:52 +0300, Maxim Uvarov wrote:
>
> [nip]
>> maybe just define it as:
>>
>> #define ODP_CPUMASK_SIZE __CPU_SETSIZE
>> ?
> First of all, I don't think it's appropriate to set it to __CPU_SETSIZE but it
> should be (at most) the one ex
On Mon, 2017-02-27 at 18:52 +0300, Maxim Uvarov wrote:
[nip]
> maybe just define it as:
>
> #define ODP_CPUMASK_SIZE __CPU_SETSIZE
> ?
First of all, I don't think it's appropriate to set it to __CPU_SETSIZE but it
should be (at most) the one exposed by one level up header (e.g. sched.h).
However
after some thinking
and looking to that link:
https://www.sourceware.org/ml/libc-alpha/2016-08/msg00236.html
I see that we do not know how many cpus will be there. And the more
clean fix will be dynamic allocation instead of static arrays.
Maxim.
On 02/27/17 18:42, Marco Varlese wrote:
> Cool.
On 02/27/17 18:42, Marco Varlese wrote:
> Cool. I posted here because it appeared strange to me to get that error...
>
> On my system I checked that:
> CPU_SETSIZE is 4096 as first defined as __CPU_SETSIZE in bits/sched.h and then
> as CPU_SETSIZE in sched.h
> bits/sched.h:# define __CPU_SETSIZE
Cool. I posted here because it appeared strange to me to get that error...
On my system I checked that:
CPU_SETSIZE is 4096 as first defined as __CPU_SETSIZE in bits/sched.h and then
as CPU_SETSIZE in sched.h
bits/sched.h:# define __CPU_SETSIZE 4096
sched.h:# define CPU_SETSIZE __CPU_SETSIZE
Thanks. I'm not sure if ODP has been tested in that environment. My guess
is it's something simple. That assert is testing sizeof(cpu_set_t) and it
sounds like that's different in Suse then, say, Ubuntu.
On Mon, Feb 27, 2017 at 8:47 AM, Marco Varlese
wrote:
> OS: openSUSE Leap 42.2
> Compiler: g
OS: openSUSE Leap 42.2
Compiler: gcc-6
Kernel: 4.10.0-rc4-1.g4f824f1-default
Cheers,
Marco
On Mon, 2017-02-27 at 08:44 -0600, Bill Fischofer wrote:
> What environment are you running in (OS, compiler, service levels, etc.)?
>
> > On Mon, Feb 27, 2017 at 8:35 AM, Marco Varlese
> > wrote:
> >
What environment are you running in (OS, compiler, service levels, etc.)?
On Mon, Feb 27, 2017 at 8:35 AM, Marco Varlese
wrote:
> Hi,
>
> I've pulled latest code from the git repo and got into a compile-time
> error.
>
> I followed the steps provided in the README file under
> platform/linux-gen
Hi,
I've pulled latest code from the git repo and got into a compile-time error.
I followed the steps provided in the README file under platform/linux-generic
which are:
./bootstrap
./configure
./make
Please, see below the output of the compilation.
CC _fdserver.lo
CC _ishm.lo
16 matches
Mail list logo
