Re: [systemd-devel] [RFC] Initial libsystemd-asyncns commit

2014-01-03 Thread Daniel Buch
Yes im still working on it (Should have been finished days ago. 24 hours a day is again not enough -.-). So far i went for the threaded version, and cleaned up stuff according to this mail thread. And i updated it to match systemd with c99 null initialisation of structs etc. That might be wrong

Re: [systemd-devel] [RFC] Initial libsystemd-asyncns commit

2014-01-02 Thread Tom Gundersen
On Wed, Dec 11, 2013 at 2:41 AM, Lennart Poettering lenn...@poettering.net wrote: On Wed, 11.12.13 02:13, Daniel Buch (boogiewasth...@gmail.com) wrote: Heya, Hmm, so thinking about it I have the suspicion this should probably be linked into libsystemd-bus, and thus live in

Re: [systemd-devel] [RFC] Initial libsystemd-asyncns commit

2014-01-02 Thread Tom Gundersen
On Thu, Jan 2, 2014 at 10:53 PM, Tom Gundersen t...@jklm.no wrote: On Wed, Dec 11, 2013 at 2:41 AM, Lennart Poettering lenn...@poettering.net wrote: On Wed, 11.12.13 02:13, Daniel Buch (boogiewasth...@gmail.com) wrote: Heya, Hmm, so thinking about it I have the suspicion this should

Re: [systemd-devel] [RFC] Initial libsystemd-asyncns commit

2014-01-02 Thread Kay Sievers
On Thu, Jan 2, 2014 at 10:53 PM, Tom Gundersen t...@jklm.no wrote: On Wed, Dec 11, 2013 at 2:41 AM, Lennart Poettering lenn...@poettering.net wrote: To follow the naming scheme of the other libs we should probably call this sd-asyncs.c, and the header file should be in src/systemd/ together

Re: [systemd-devel] [RFC] Initial libsystemd-asyncns commit

2014-01-02 Thread David Timothy Strauss
Just to consider what other folks are doing, I know Fedora builds libcurl with a thread-isolated, NSS-based resolver. On a less-related note, at Pantheon improve DNS performance on servers by setting resolv.conf to localhost and running Unbound there. Unbound then uses the datacenter's recursive

Re: [systemd-devel] [RFC] Initial libsystemd-asyncns commit

2013-12-12 Thread Marcel Holtmann
Hi Lennart, why do we have to spawn threads or do forks for DNS. This looks all pretty expensive. In ConnMan for example we just wrote our own async DNS using a mainloop. Works perfectly fine and is dirt cheap. Well, we don't fork threads/processes for each call but reuse them. What

Re: [systemd-devel] [RFC] Initial libsystemd-asyncns commit

2013-12-12 Thread Andrey Borzenkov
В Thu, 12 Dec 2013 14:09:42 +0100 Marcel Holtmann mar...@holtmann.org пишет: Hi Lennart, why do we have to spawn threads or do forks for DNS. This looks all pretty expensive. In ConnMan for example we just wrote our own async DNS using a mainloop. Works perfectly fine and is dirt cheap.

Re: [systemd-devel] [RFC] Initial libsystemd-asyncns commit

2013-12-12 Thread Lennart Poettering
On Thu, 12.12.13 14:09, Marcel Holtmann (mar...@holtmann.org) wrote: Hi Lennart, why do we have to spawn threads or do forks for DNS. This looks all pretty expensive. In ConnMan for example we just wrote our own async DNS using a mainloop. Works perfectly fine and is dirt cheap.

Re: [systemd-devel] [RFC] Initial libsystemd-asyncns commit

2013-12-12 Thread Marcel Holtmann
Hi Andrey, why do we have to spawn threads or do forks for DNS. This looks all pretty expensive. In ConnMan for example we just wrote our own async DNS using a mainloop. Works perfectly fine and is dirt cheap. Well, we don't fork threads/processes for each call but reuse them. What

Re: [systemd-devel] [RFC] Initial libsystemd-asyncns commit

2013-12-12 Thread Lennart Poettering
On Thu, 12.12.13 15:20, Marcel Holtmann (mar...@holtmann.org) wrote: Hi Andrey, why do we have to spawn threads or do forks for DNS. This looks all pretty expensive. In ConnMan for example we just wrote our own async DNS using a mainloop. Works perfectly fine and is dirt cheap.

Re: [systemd-devel] [RFC] Initial libsystemd-asyncns commit

2013-12-12 Thread Marcel Holtmann
Hi Lennart, why do we have to spawn threads or do forks for DNS. This looks all pretty expensive. In ConnMan for example we just wrote our own async DNS using a mainloop. Works perfectly fine and is dirt cheap. Well, we don't fork threads/processes for each call but reuse them. What

Re: [systemd-devel] [RFC] Initial libsystemd-asyncns commit

2013-12-12 Thread Lennart Poettering
On Thu, 12.12.13 16:28, Marcel Holtmann (mar...@holtmann.org) wrote: Hi Lennart, why do we have to spawn threads or do forks for DNS. This looks all pretty expensive. In ConnMan for example we just wrote our own async DNS using a mainloop. Works perfectly fine and is dirt cheap.

Re: [systemd-devel] [RFC] Initial libsystemd-asyncns commit

2013-12-11 Thread Thomas H.P. Andersen
On Wed, Dec 11, 2013 at 2:41 AM, Lennart Poettering lenn...@poettering.net wrote: On Wed, 11.12.13 02:13, Daniel Buch (boogiewasth...@gmail.com) wrote: Heya, Hmm, so thinking about it I have the suspicion this should probably be linked into libsystemd-bus, and thus live in

Re: [systemd-devel] [RFC] Initial libsystemd-asyncns commit

2013-12-10 Thread Marcel Holtmann
Hi Daniel, Reindentation is done to fit systemd --- Makefile.am | 23 + src/libsystemd-asyncns/asyncns.c | 1513 + src/libsystemd-asyncns/asyncns.h | 163 src/libsystemd-asyncns/test-asyncns.c | 178 4 files

Re: [systemd-devel] [RFC] Initial libsystemd-asyncns commit

2013-12-10 Thread Lennart Poettering
On Wed, 11.12.13 02:13, Daniel Buch (boogiewasth...@gmail.com) wrote: Heya, Hmm, so thinking about it I have the suspicion this should probably be linked into libsystemd-bus, and thus live in src/libsystemd-bus/. The reason for this is cyclic deps: libsystemd-bus really should make use of this

Re: [systemd-devel] [RFC] Initial libsystemd-asyncns commit

2013-12-10 Thread Lennart Poettering
On Wed, 11.12.13 02:36, Marcel Holtmann (mar...@holtmann.org) wrote: why do we have to spawn threads or do forks for DNS. This looks all pretty expensive. In ConnMan for example we just wrote our own async DNS using a mainloop. Works perfectly fine and is dirt cheap. Well, we don't fork