Regarding Netmap internal memory allocation.

To Luigi and to whom may be able to help Hello all. Is it possible to reduce the size of the memory buffer allocated by the netmap module? I'm asking this because I was implementing some testing code, using NICs and a Tap device in an OpenWRT VM with 64MB of RAM. Because of the small RAM amount,

Re: Regarding Netmap internal memory allocation.

Update: I noticed that the netmap module was still crashing, after changing the OpenWRT VM ram to 256MB. I now raised to 1GB and it no longer crashed. The netmap module is now consuming about 350MB of Ram, which for my objectives is just too much... On 30 December 2014 at 14:06, Carlos Ferreira

Re: Regarding Netmap internal memory allocation.

you can reduce the amount of ram (buffers, mostly) by tweaking the values in netmap_mem2.c :: struct netmap_obj_params netmap_params[NETMAP_POOLS_NR] = { ... } or you can simply modify the constant netmap_mem2.h:#define NETMAP_BUF_MAX_NUM 20*4096*2 to something smaller that suits an openwrt box

Re: Regarding Netmap internal memory allocation.

Ok thanks. I was hoping not having to recompile the module, but it's ok. Thank you for the info! On 30 December 2014 at 15:38, Luigi Rizzo wrote: > you can reduce the amount of ram (buffers, mostly) by > tweaking the values in netmap_mem2.c :: > struct netmap_obj_params netmap_params[NETMAP_POO

[Bug 194672] [carp] Changing advskew to 0 from another value doesn't work

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=194672 --- Comment #3 from Renato Botelho --- Created attachment 151123 --> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=151123&action=edit 2nd attempt, fix also advbase check There is one more issue, advbase should be >= 1 and <= 255, i

Re: Regarding Netmap internal memory allocation.

You mean netmap_mem2.c ? It was there where I found the NETMAP_BUF_MAX_NUM define. On 30 December 2014 at 15:43, Carlos Ferreira wrote: > Ok thanks. I was hoping not having to recompile the module, but it's ok. > Thank you for the info! > > > On 30 December 2014 at 15:38, Luigi Rizzo wrote: >

Re: Regarding Netmap internal memory allocation.

By the way, another question. Is there a way to not compile the code regarding the VALE switch? I'm only interested in using netmap with Tap Devices and NICs, so I was hoping to save some memory. On 30 December 2014 at 15:47, Carlos Ferreira wrote: > You mean netmap_mem2.c ? It was there where I

Re: Regarding Netmap internal memory allocation.

you don't need to recompile, on linux those values are accessible under /sys/modules/netmal_lin/parameters (on FreeBSD they are sysctl variables) cheers luigi On Tue, Dec 30, 2014 at 4:43 PM, Carlos Ferreira wrote: > Ok thanks. I was hoping not having to recompile the module, but it's ok. > Tha

Re: Regarding Netmap internal memory allocation.

you can #undefine WITH_VALE. But it is only 20K of code (and 150K of data structures, which you can further reduce by lowering NM_BRIDGS). The saving is probably not worth the effort. cheers luigi On Tue, Dec 30, 2014 at 5:08 PM, Carlos Ferreira wrote: > By the way, another question. > Is there

[Bug 194672] [carp] Changing advskew to 0 from another value doesn't work

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=194672 --- Comment #4 from Renato Botelho --- Please ignore second patch, it has issues, will send a new one shortly -- You are receiving this mail because: You are the assignee for the bug. ___ freebs

Re: Regarding Netmap internal memory allocation.

Ok, I'm having some trouble in tuning the amount of memory for netmap. I have been following the man page from FreeBSD in other to understand the values at /sys/modules/netmap/parameters for linux but I'm having some trouble in under

Tying down network interfaces

Hi, I have two network interfaces as follows: sis0: port 0xa400-0xa4ff mem 0xd580-0xd5800fff irq 9 at device 9.0 on pci0 sis1: port 0x9400-0x94ff mem 0xd480-0xd4800fff irq 11 at device 12.0 on pci0 When sis0 breaks down, sis1 gets renumbered as sis0, wreaking havoc (mostly on my brains

Re: Regarding Netmap internal memory allocation.

On Tue, Dec 30, 2014 at 6:38 PM, Carlos Ferreira wrote: > Ok, I'm having some trouble in tuning the amount of memory for netmap. > > I have been following the man page from FreeBSD in other to understand the > values at /sys/modules/netmap/parameters for linux but I'm having some > trouble in unde

Re: Regarding Netmap internal memory allocation.

Well... due to budget constraints I'm using USB 100Mb ports :) This is for experimental purposes only for now. Btw, can netmap work with wireless interfaces? I believe you once answered this question, but I could not find it in the mail list. On 30 December 2014 at 18:40, Luigi Rizzo wrote: > O

[Bug 194672] [carp] Changing advskew to 0 from another value doesn't work

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=194672 --- Comment #5 from Renato Botelho --- Created attachment 151128 --> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=151128&action=edit 3rd version - Fix advskew and advbase checks, set default advbase for new entries This version ch

Re: Tying down network interfaces

On Tue, 30 Dec 2014 19:02:30 +0100 Martin Birgmeier wrote > Hi, > > I have two network interfaces as follows: > > sis0: port 0xa400-0xa4ff mem > 0xd580-0xd5800fff irq 9 at device 9.0 on pci0 > sis1: port 0x9400-0x94ff mem > 0xd480-0xd4800fff irq 11 at device 12.0 on pci0 > > When sis

Re: Tying down network interfaces

On Dec 30, 2014 10:02 AM, "Martin Birgmeier" wrote: > > Hi, > > I have two network interfaces as follows: > > sis0: port 0xa400-0xa4ff mem > 0xd580-0xd5800fff irq 9 at device 9.0 on pci0 > sis1: port 0x9400-0x94ff mem > 0xd480-0xd4800fff irq 11 at device 12.0 on pci0 > > When sis0 breaks