<html>
<head>
<meta content="text/html; charset=utf-8" http-equiv="Content-Type">
</head>
<body bgcolor="#FFFFFF" text="#000000">
<p><font face="Ubuntu">Hi David,</font><br>
</p>
<br>
<div class="moz-cite-prefix">Le 06/04/2017 à 16:14, David Ahern a
écrit :<br>
</div>
<blockquote
cite="mid:94ba269f-4db1-4eb6-74ca-950f3809ed5c@cumulusnetworks.com"
type="cite">
<pre wrap="">On 4/6/17 10:12 AM, Donald Sharp wrote:
</pre>
<blockquote type="cite">
<pre wrap="">I'm not sure I would call it 'waste'. The solution, as I understand
</pre>
</blockquote>
<pre wrap="">
There is no waste.
</pre>
<blockquote type="cite">
<pre wrap="">it, allocates the appopriate amount of memory to handle the # of
labels handed to it with a *limit* of 4k bytes to the size that is
alloc'ed internally to the kernel. This way they are keeping the data
structure limit to the maximum size of a page on some platforms at
worse case.
</pre>
</blockquote>
<pre wrap="">
exactly.</pre>
</blockquote>
So, if I correctly understand, this means that we could manage for
example 136 segment paths of 30 labels each, 256 segment paths of 16
labels each, 1024 segment paths of 4 labels, ... In other words, the
sum of all label stacks of all segment paths must fit under the 4k
bytes limit. I understand that we must put a limit, but 4k bytes is
short. Very short. At the maximum it only authorizes 4k connexions
with only one label i.e. only 4K LDP, RSVP-TE or MP-BGP paths.<br>
<br>
So, is there a possibility to request another chunk of 4k bytes to
increase the number of managed paths ? or this limit is hard coded
at the compilation ?<br>
<br>
Regards<br>
<br>
Olivier<br>
<blockquote
cite="mid:94ba269f-4db1-4eb6-74ca-950f3809ed5c@cumulusnetworks.com"
type="cite">
<pre wrap="">
</pre>
</blockquote>
<br>
</body>
</html>