All of lore.kernel.org
 help / color / mirror / Atom feed
From: Sven Eckelmann <sven@narfation.org>
To: b.a.t.m.a.n@lists.open-mesh.org
Subject: Re: [B.A.T.M.A.N.] Interface limit 127 in bat0?!
Date: Tue, 21 Feb 2017 18:13:00 +0100	[thread overview]
Message-ID: <1535884.R2pzemgNJL@bentobox> (raw)
In-Reply-To: <20170221162435.GC25818@lunn.ch>

[-- Attachment #1: Type: text/plain, Size: 1014 bytes --]

On Dienstag, 21. Februar 2017 17:24:35 CET Andrew Lunn wrote:
> > |Error - can't write to file
> > '/sys/class/net/gre127/batman_adv/mesh_iface': Cannot allocate memory|
> 
> As the message suggests, you are out of memory. This is not a BATMAN
> limit, it is a limit from the amount of RAM you have in your device.

contiguous kernel memory to store the per-interface originator data - to
be more precise. See batadv_iv_ogm_orig_add_if and all kmalloc*/kfree
references with bcast_own/bcast_own_sum

On Dienstag, 21. Februar 2017 17:19:42 CET jens wrote:
> i observe a limit of 127 interfaces which can be hooked into bat0
> where do i find this limit, or does somebody can tell me more about
> this? Or, if it is a good idea to circumwent this at all? Or, if its
> even possible in actual protocoll structure.

And we had this discussion before [1]. Not sure why you are now
pretending that this never happened.

Kind regards,
	Sven

[1] https://lists.open-mesh.org/pipermail/b.a.t.m.a.n/2017-January/016824.html

[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 833 bytes --]

  parent reply	other threads:[~2017-02-21 17:13 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-02-21 16:19 [B.A.T.M.A.N.] Interface limit 127 in bat0?! jens
2017-02-21 16:24 ` Andrew Lunn
     [not found]   ` <e7b68377-8a30-8f00-a247-163957f01ef4@viisauksena.de>
2017-02-21 17:00     ` Andrew Lunn
2017-02-21 17:13   ` Sven Eckelmann [this message]
2017-02-21 17:18     ` jens

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=1535884.R2pzemgNJL@bentobox \
    --to=sven@narfation.org \
    --cc=b.a.t.m.a.n@lists.open-mesh.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.