Hi, On Mon, 26 Sep 2005, tedemo wrote: > >Check out the real size of the hashes by searching the kernel log:0 > >"rehashing of set <foo> triggered: hashsize grows from <n> to <m>". > The size for the nethash, reported in the log is arround 20mo the first > time it I run : > ipset --restore < ip.sets When the hash size is about 20 million entries, that alone requires ~80MB physical memory. If resizing is triggered, at least two times of that amount of memory is needed temporarily. > I deleted each set (using ipset -X on each other) and the recreated them, > the size of the nethash went to 40Mo > > A few reloads later its size is 90Mo. Please write it exactly what you do and what happens. Do you create, fill up and delete the *same* sets with exactly the *same* content, in a loop? > NB: The set definition file has been created manualy to avoid hundred > thousand calls to "ipset -A" > (i.e. without calling ipset --save). Can this cause troubles ? No. What is your kernel and ipset versions? Best regards, Jozsef - E-mail : kadlec@xxxxxxxxxxxxxxxxx, kadlec@xxxxxxxxxxxxxxx PGP key : http://www.kfki.hu/~kadlec/pgp_public_key.txt Address : KFKI Research Institute for Particle and Nuclear Physics H-1525 Budapest 114, POB. 49, Hungary
