On Friday 2010-11-26 20:48, Jozsef Kadlecsik wrote: >> > >> >What is that initial data handling in dumps for? >> >> Making an atomic snapshot/copy of the table. A userspace client >> could take almost indefinitely on retrieving a table, so it is >> possible that something else changes tables meanwhile. > >Why don't you lock the tables during dumping? That way the tables won't >change, whatever long time the dump takes. Snapshotting the table looks as >wasting memory and time. For that to work, I would have to use a locking primitive that can be held across returns to userspace, which leaves semaphores as the only option and, ya, I didn't quite feel like using _that_. Also sounds a bit like a killer if an admin cannot update a table just because he forgot some dumper process in the background in suspended state. :-/ -- To unsubscribe from this list: send the line "unsubscribe netfilter-devel" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
