From: Karel Zak <kzak@redhat.com>
To: "Aurélien Lajoie" <orel@melix.net>
Cc: Util-Linux <util-linux@vger.kernel.org>,
Stanislav Brabec <sbrabec@suse.cz>,
"Trapp, Michael" <michael.trapp@sap.com>
Subject: Re: libuuid related tasks for next v2.39
Date: Tue, 12 Apr 2022 12:34:51 +0200 [thread overview]
Message-ID: <20220412103451.pve2pe3ey3rcxfuq@ws.net.home> (raw)
In-Reply-To: <CAA0A08XAF2eWScVKQ1Jd0vUPfHzZw8PAtiS-jRbom0EvRQ+Zsg@mail.gmail.com>
On Fri, Apr 01, 2022 at 11:49:17AM +0200, Aurélien Lajoie wrote:
> What about nice helpers to get fast access to the different part of the
> uuid?
I'm not sure if I understand. What do you mean with the helpers?
> We need to keep an eye on performance, php uuid code was more perf than the
> previous version of our lib.
Yes, printf sucks. It's fixed now. Thanks to you :-)
> Perhaps add some test to catch big impact on serialization and
> deserialization
Good point, maybe it's something we can add to (suggested)
uuidinfo command.
Karel
--
Karel Zak <kzak@redhat.com>
http://karelzak.blogspot.com
next prev parent reply other threads:[~2022-04-12 11:48 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-01 9:21 libuuid related tasks for next v2.39 Karel Zak
2022-04-11 13:36 ` Stanislav Brabec
2022-04-12 11:36 ` Karel Zak
[not found] ` <AM9PR02MB70447FD1C9D326ABAF7ABFE8F9E69@AM9PR02MB7044.eurprd02.prod.outlook.com>
2022-04-11 13:45 ` Stanislav Brabec
[not found] ` <CAA0A08XAF2eWScVKQ1Jd0vUPfHzZw8PAtiS-jRbom0EvRQ+Zsg@mail.gmail.com>
2022-04-12 10:34 ` Karel Zak [this message]
[not found] ` <CAA0A08VmzKTzFCEqnFP9tw50zgx4iPsif_BktuRSAvfm3hH52w@mail.gmail.com>
2022-04-12 11:44 ` Karel Zak
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=20220412103451.pve2pe3ey3rcxfuq@ws.net.home \
--to=kzak@redhat.com \
--cc=michael.trapp@sap.com \
--cc=orel@melix.net \
--cc=sbrabec@suse.cz \
--cc=util-linux@vger.kernel.org \
/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;
as well as URLs for NNTP newsgroup(s).