On 04/11/2016 01:28 AM, Erik Hugne wrote:
> On Apr 10, 2016 15:27, "Leon Pollak" wrote:
>> After your answer I again looked through the both manuals and did not find
>> anything saying that connectionless messaging allows drops. Vice verse,
> the
>> programmer's manual explicitly states that "TI
On Apr 10, 2016 15:27, "Leon Pollak" wrote:
>
> After your answer I again looked through the both manuals and did not find
> anything saying that connectionless messaging allows drops. Vice verse,
the
> programmer's manual explicitly states that "TIPC is designed to be a
reliable
> messaging mecha
On Friday 01 April 2016 15:02:05 Jon Maloy wrote:
> > I saw that the problem is in the lack of memory.
> > I also made a simple stress test (one side sends in a loop) and received
> > this problem immediately.
> > But User's Manual states that if there is no room for the receiving side
> > to acc
> -Original Message-
> From: Leon Pollak [mailto:le...@plris.com]
> Sent: Wednesday, 30 March, 2016 11:05
> To: Jon Maloy
> Cc: tipc-discussion@lists.sourceforge.net
> Subject: Re: [tipc-discussion] kernel page allocation problem
>
> On Wednesday 30 March 2016
On Wednesday 30 March 2016 14:40:58 Jon Maloy wrote:
> Hi Leon,
> I took a quick look at your dump, and to me it looks like you have simply
run out of memory. I think that is the first thing you should look at.
> As for the most recent code version to use, I cannot give you aby definite
answer, s
have at hand first.
BR
///jon
> -Original Message-
> From: Leon Pollak [mailto:le...@plris.com]
> Sent: Wednesday, 30 March, 2016 03:45
> To: Jon Maloy
> Cc: tipc-discussion@lists.sourceforge.net
> Subject: Re: [tipc-discussion] kernel page allocation problem
>
>
Hi, Jon.
Thank you for the reply.
I can't upgrade the kernel to any other version, because it is an embedded
system based on TI DM8148 processor and there are a lot of drivers and
firmware working with it.
As far as I understand, I can change/upgrade the TIPC files only. But I wasn't
able to fi
Hi Leon,
Yes, you are running TIPC 2.0, but that does not really mean much. The version
number hasn't changed the last 4-5 years, while huge parts of the code has been
fundamentally rewritten during that period.
There were several issues like the one you have encountered, and almost all of
them