From: Constantin Musca <constantinx.musca@intel.com>
To: Ross Burton <ross.burton@intel.com>
Cc: openembedded-core@lists.openembedded.org
Subject: Re: [PATCH] libnss-mdns: fix mDNS resolving speed
Date: Fri, 28 Sep 2012 17:16:43 +0300 [thread overview]
Message-ID: <5065B14B.6080204@intel.com> (raw)
In-Reply-To: <CF4AF9D3EAC5423B9F39CDED1CA5411C@intel.com>
On 09/28/2012 04:05 PM, Ross Burton wrote:
> On Friday, 28 September 2012 at 12:55, Constantin Musca wrote:
>> Tests:
>>
>> 1. Without fix:
>> real 0m4.461s
>> user 0m0.034s
>> sys 0m0.086s
>>
>> 2. With fix:
>> real 0m0.842s
>> user 0m0.066s
>> sys 0m0.122s
>>
>> As you can see, there is a speed improvement.
> Excellent.
>
> I'll ask it before Martin does - should we handle upgrading users from an old libnss-mdns with the old line?
>
> Ross
>
>
I'll send patch v2 which handles upgrading.
Constantin
prev parent reply other threads:[~2012-09-28 15:24 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-09-28 8:18 [PATCH] libnss-mdns: fix mDNS resolving speed Constantin Musca
2012-09-28 9:40 ` Burton, Ross
2012-09-28 8:48 ` Constantin Musca
2012-09-28 9:46 ` Burton, Ross
2012-09-28 8:53 ` Constantin Musca
2012-09-28 11:55 ` Constantin Musca
2012-09-28 13:05 ` Ross Burton
2012-09-28 14:16 ` Constantin Musca [this message]
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=5065B14B.6080204@intel.com \
--to=constantinx.musca@intel.com \
--cc=openembedded-core@lists.openembedded.org \
--cc=ross.burton@intel.com \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox