From: Sunitha Harish <sunithaharish04@gmail.com>
To: Patrick Williams <patrick@stwcx.xyz>
Cc: openbmc@lists.ozlabs.org, apparao.puli@linux.intel.com,
edtanous@google.com
Subject: Re: pthreads at bmcweb
Date: Mon, 18 Jan 2021 15:19:20 +0530 [thread overview]
Message-ID: <759a5406-aff0-3097-d602-ac4787c4c38b@gmail.com> (raw)
In-Reply-To: <X/2ehAMgWkmUZoAr@heinlein>
On 12-01-2021 18:35, Patrick Williams wrote:
> On Wed, Jan 06, 2021 at 01:32:11PM +0530, Sunitha Harish wrote:
>> Ed's suggestion is not to use the pthreads, instead implement
>> alternatives to do the same job, so that the binary size is kept
>> minimum. He mentioned: /"//Considering that's a ~30% increase in binary
>> size to support one line off code, and most systems are already at their
>> binary size limit, no, that's not going to be acceptable. We can either
>> patch boost to use this
>> //https://man7.org/linux/man-pages/man3/getaddrinfo_a.3.html
>> <https://man7.org/linux/man-pages/man3/getaddrinfo_a.3.html>//or we
>> could build our own resolver type that calls that underneath. This was
>> based on a quick lookthrough of solutions in Google. I'm open to other
>> ideas here". /
> Since we're using systemd and we have the `resolved` feature turned on,
> why not just send an async dbus message to the resolved.service?
>
> ```
> $ busctl introspect org.freedesktop.resolve1 /org/freedesktop/resolve1 | grep ResolveHostname
> .ResolveHostname method isit a(iiay)st -
> ```
>
> https://www.freedesktop.org/software/systemd/man/org.freedesktop.resolve1.html
Thank you Patrick. I will try implementing this and verify if all the
async event notification scenarios works good.
Regards,
Sunitha
next prev parent reply other threads:[~2021-01-18 9:51 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-06 8:02 pthreads at bmcweb Sunitha Harish
2021-01-06 18:12 ` Milton Miller II
2021-01-12 8:48 ` Sunitha Harish
2021-01-12 13:05 ` Patrick Williams
2021-01-18 9:49 ` Sunitha Harish [this message]
2021-01-19 16:48 ` Ed Tanous
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=759a5406-aff0-3097-d602-ac4787c4c38b@gmail.com \
--to=sunithaharish04@gmail.com \
--cc=apparao.puli@linux.intel.com \
--cc=edtanous@google.com \
--cc=openbmc@lists.ozlabs.org \
--cc=patrick@stwcx.xyz \
/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.