From: Noah Goldstein <goldstein.w.n@gmail.com>
To: Sunil Pandey <skpgkp2@gmail.com>
Cc: Paul Eggert <eggert@cs.ucla.edu>,
libc-alpha@sourceware.org, hjl.tools@gmail.com
Subject: Re: [PATCH] x86_64: Implement AVX2 version of strlcpy/wcslcpy function
Date: Fri, 30 Jun 2023 18:27:47 -0500 [thread overview]
Message-ID: <CAFUsyfJuftiP17f6abvwDoUtXRuupTrsCcVsfmcQ5=fFSWYSAg@mail.gmail.com> (raw)
In-Reply-To: <CAFUsyf+F=biiqgsaBajfSamutfis_tCe7b2ikAZGN4jzJ15qiQ@mail.gmail.com>
On Fri, Jun 30, 2023 at 6:22 PM Noah Goldstein <goldstein.w.n@gmail.com> wrote:
>
> On Fri, Jun 30, 2023 at 5:21 PM Sunil Pandey <skpgkp2@gmail.com> wrote:
> >
> >
> >
> > On Fri, Jun 30, 2023 at 2:27 PM Paul Eggert <eggert@cs.ucla.edu> wrote:
> >>
> >> On 2023-06-30 14:04, Noah Goldstein via Libc-alpha wrote:
> >> > Think we should at the very least wait for the generic strlcpy codes
> >> > to land first.
> >>
> >> Let's not optimize these functions at all, unless there's good and
> >> measured reason to do so. In practice I expected they're called with
> >> small sizes for which optimization is a net minus as it consumes
> >> valuable maintenance time with no real benefit.
> >
> >
> > Hi Paul,
> >
> > Attached is strcpy/wcslcpy microbenchmark data based on Noah strlcpy/wcslcpy microbenchmark patch.
> >
> I don't think the concern is that we can beat the generic impl (which hasn't
> even landed yet AFAICT), it whether doing so makes sense given the
> usage/goal of the functions.
>
That being said, I'm generally in favor of adding optimized versions since
we happen to be a position where at least several developers find it worth
their time to maintain, but not before the generic versions have landed.
> > https://sourceware.org/pipermail/libc-alpha/2023-April/147557.html
> >
> > Thanks,
> > Sunil
next prev parent reply other threads:[~2023-06-30 23:28 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-30 20:48 Sunil K Pandey
2023-06-30 21:04 ` Noah Goldstein
2023-06-30 21:27 ` Paul Eggert
2023-06-30 22:21 ` Sunil Pandey
2023-06-30 23:22 ` Noah Goldstein
2023-06-30 23:27 ` Noah Goldstein [this message]
2023-07-03 16:30 ` Paul Eggert
2023-07-03 18:40 ` Noah Goldstein
2023-07-03 18:54 ` Adhemerval Zanella Netto
2023-07-03 21:14 ` Paul Eggert
2023-07-03 22:04 ` Gabriel Ravier
2023-07-03 23:12 ` Paul Eggert
2023-07-04 7:45 ` Andreas Schwab
2023-07-03 12:55 ` Adhemerval Zanella Netto
2023-07-01 9:41 ` Florian Weimer
2023-07-02 1:22 ` Noah Goldstein
2023-07-02 6:51 ` Florian Weimer
2023-07-02 16:55 ` Noah Goldstein
2023-07-02 17:02 ` Florian Weimer
2023-07-02 17:03 ` Noah Goldstein
2023-07-02 18:37 ` Sunil Pandey
2023-07-02 18:54 ` Noah Goldstein
2023-07-03 1:03 ` Sunil Pandey
2023-07-03 1:47 ` Noah Goldstein
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='CAFUsyfJuftiP17f6abvwDoUtXRuupTrsCcVsfmcQ5=fFSWYSAg@mail.gmail.com' \
--to=goldstein.w.n@gmail.com \
--cc=eggert@cs.ucla.edu \
--cc=hjl.tools@gmail.com \
--cc=libc-alpha@sourceware.org \
--cc=skpgkp2@gmail.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).