git/list[1] front-page[2] threads[3] people[4] search[5] about
 

Re: [PATCHv2] attr: convert to new threadsafe API

From
Junio C Hamano <gitster@pobox.com>
Date
Oct 12, 2016, 21:28 UTC
Message-ID
<xmqqh98h2r5t.fsf@gitster.mtv.corp.google.com>
In-Reply-To
<20161011235951.8358-1-sbeller@google.com>
Stefan Beller <sbeller@google.com> writes:
> This version adds the actual thread safety,
> that is promised in the documentation, however it doesn't add any optimization,
> i.e. it's a single global lock. But as we do not expect contention, that is fine.

Because we have to start _somewhere_, I agree it is a good approach to first try the simplest implementation and then optimize later, but is it an agreed consensus that we do not expect contention?

Previous: Stefan BellerNext: Stefan Beller
Message 14 of 16 in “[PATCHv2] attr: convert to new threadsafe API”
  1. Stefan BellerOct 11, 2016
  2. Junio C HamanoOct 12, 2016
  3. Stefan BellerOct 12, 2016
  4. Junio C HamanoOct 12, 2016
  5. Stefan BellerOct 12, 2016
  6. Junio C HamanoOct 12, 2016
  7. Junio C HamanoOct 12, 2016
  8. Johannes SixtOct 12, 2016
  9. Junio C HamanoOct 12, 2016
  10. Stefan BellerOct 12, 2016
  11. Junio C HamanoOct 12, 2016
  12. Jacob KellerOct 12, 2016
  13. Stefan BellerOct 12, 2016
  14. Junio C HamanoOct 12, 2016
  15. Stefan BellerOct 12, 2016
  16. Junio C HamanoOct 12, 2016

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.