From: Maxim Kuvyrkov <maxim@codesourcery.com>
To: Roland McGrath <roland@hack.frob.com>
Cc: Andrew Haley <aph@redhat.com>, David Miller <davem@davemloft.net>,
"Joseph S. Myers" <joseph@codesourcery.com>,
Richard Sandiford <rdsandiford@googlemail.com>,
<libc-ports@sourceware.org>,
GLIBC Devel <libc-alpha@sourceware.org>,
Chris Metcalf <cmetcalf@tilera.com>
Subject: Re: [PATCH] Unify pthread_spin_[try]lock implementations.
Date: Wed, 15 Aug 2012 16:39:00 -0000 [thread overview]
Message-ID: <BE128C9A-CABC-4E04-A48E-316EAE8E0C64@codesourcery.com> (raw)
In-Reply-To: <20120815162637.B74982C0F2@topped-with-meat.com>
On 16/08/2012, at 4:26 AM, Roland McGrath wrote:
>> 2012-07-09 Maxim Kuvyrkov <maxim@codesourcery.com>
>
> The indentation here is funny so I don't know if that's just how you were
> quoting the fragment in the message or if you meant to indent the header
> line in ChangeLog (which you should not). Remember to use the date of
> commit in the header line.
This is just an indentation artifact in git commit log. It will be properly formatted in the actual ChangeLog file.
>
>> * nptl/pthread_spin_lock.c: New file.
>> * nptl/pthread_spin_trylock.c: New file.
>
> These go in nptl/ChangeLog and don't get the "nptl/" prefix.
This I didn't notice. Thanks.
>
>> ports/
>
> These go in the separate ChangeLog.{arm,hppa,m68k,mips} files.
> From the way you quoted the fragments it wasn't clear if that's
> what you meant.
This I know.
>
>> +#define SPIN_LOCK_READS_BETWEEN_CMPXCHG 1000
>> +#include_next <nptl/pthread_spin_lock.c>
>
> You don't use #include_next when you're giving the exact full file name
> like this. Just use #include.
The machine-specific pthread_spin_lock.c files go to ports/sysdeps/<machine>/nptl/pthread_spin_lock.c, which comes first in sysdeps search path before the generic nptl/pthread_spin_lock.c. So it is either '#include_next <nptl/pthread_spin_lock.c>' or '#include "../../../../nptl/pthread_spin_lock.c"'. The former looks less ugly than the later.
>
>
> Aside from the log nits, the generic additions look fine to me. You can
> commit those as soon as one of the affected machine's maintainers agrees.
> For each machine, the changes need to be approved by that machine's
> maintainer. I'm not the maintainer for any those machines, but I would be
> inclined to insist that each definition of SPIN_LOCK_READS_BETWEEN_CMPXCHG
> have a comment giving the machine-specific rationale for the choice of value.
> I wouldn't wait for all the machine maintainers before committing the
> generic parts and whichever machine(s) are approved first. Each machine's
> bits can come along later as those approvals arrive.
OK.
Thanks for the review,
--
Maxim Kuvyrkov
CodeSourcery / Mentor Graphics
next prev parent reply other threads:[~2012-08-15 16:39 UTC|newest]
Thread overview: 34+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-06-14 4:36 [PATCH 2/3, MIPS] Rewrite MIPS' pthread_spin_[try]lock using __atomic_* builtins Maxim Kuvyrkov
2012-06-28 23:10 ` Joseph S. Myers
2012-07-11 5:58 ` [PATCH] Unify pthread_spin_[try]lock implementations Maxim Kuvyrkov
2012-07-11 8:15 ` Roland McGrath
2012-07-11 8:25 ` David Miller
2012-07-11 8:44 ` Andrew Haley
2012-07-11 8:54 ` Maxim Kuvyrkov
2012-07-11 9:02 ` Andrew Haley
2012-07-11 9:05 ` Maxim Kuvyrkov
2012-07-11 11:22 ` Roland McGrath
2012-07-11 14:52 ` Chris Metcalf
2012-07-11 22:16 ` Maxim Kuvyrkov
2012-07-25 18:13 ` Roland McGrath
2012-07-25 19:04 ` Chris Metcalf
2012-07-25 20:22 ` Roland McGrath
2012-07-25 20:29 ` Chris Metcalf
2012-07-25 20:43 ` Roland McGrath
2012-08-15 3:17 ` Maxim Kuvyrkov
2012-08-15 16:27 ` Roland McGrath
2012-08-15 16:39 ` Maxim Kuvyrkov [this message]
2012-08-15 16:44 ` Roland McGrath
2012-08-15 16:53 ` Maxim Kuvyrkov
2012-08-15 16:56 ` Roland McGrath
2012-08-15 17:05 ` Maxim Kuvyrkov
2012-08-15 17:05 ` Jeff Law
2012-08-15 17:11 ` Roland McGrath
2012-08-15 17:24 ` Jeff Law
2012-08-15 16:40 ` Joseph S. Myers
2012-08-15 16:43 ` Carlos O'Donell
2012-08-15 22:00 ` Andreas Schwab
2012-08-16 10:21 ` Torvald Riegel
2012-08-16 12:40 ` Chris Metcalf
2012-08-22 23:16 ` Maxim Kuvyrkov
2012-07-11 8:26 ` Maxim Kuvyrkov
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=BE128C9A-CABC-4E04-A48E-316EAE8E0C64@codesourcery.com \
--to=maxim@codesourcery.com \
--cc=aph@redhat.com \
--cc=cmetcalf@tilera.com \
--cc=davem@davemloft.net \
--cc=joseph@codesourcery.com \
--cc=libc-alpha@sourceware.org \
--cc=libc-ports@sourceware.org \
--cc=rdsandiford@googlemail.com \
--cc=roland@hack.frob.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).