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

Re: [GSoC] Improving parallelism

From
Felipe Tanus <fotanus@gmail.com>
Date
Mar 21, 2012, 18:06 UTC
Message-ID
<CANELHzP+Kr99uLRRbmrfDzjrNn-eC-zgAfJy1Gct81nXfyrP0w@mail.gmail.com>
In-Reply-To
<87haxit95q.fsf@thomas.inf.ethz.ch>
On Wed, Mar 21, 2012 at 9:45 AM, Thomas Rast <trast@student.ethz.ch> wrote:
> Felipe Tanus <fotanus@gmail.com> writes:
[...]
>
>  1. Rework the pack access mechanisms to allow the maximum possible
>    parallel access.
>
[...]
Show 9 quoted lines
> I think (1.) is the most important part simply because without (1.) the
> other two are totally meaningless.  So I'd rather you not focus too hard
> on the command list.  However, correctly identifying more commands where
> pack access is the hotspot, and backing that up with numbers, may be a
> good way to show your understanding of the matter.
>
> For further reading, you should start with the discussions surrounding
> git-grep threading around
>
[...]

Hi Thomas, thank you for your answer, and more than it, thank you for point me to the right direction :-)

I followed the discussions you pointed out and it was very helpful. If I get it right, what you expect to be in the proposal is an analysis of what should be modified in the pack access mechanism because it will be used by the commands we will work on, and thus they should be thread safe and have a better performance. To achieve this I'll have to go through the sha1_file.c file and come with an idea of how to improve the parallelism on it. Is that what you expect for a good work in this summer?

Regards,
-- 
Felipe de Oliveira Tanus
E-mail: fotanus@gmail.com
Site: http://www.inf.ufrgs.br/~fotanus/
-----
"All we have to decide is what to do with the time that is given us." - Gandalf
Previous: Thomas Rast
Message 5 of 5 in “[GSoC] Improving parallelism”
  1. Felipe TanusMar 17, 2012
  2. Nguyen Thai Ngoc DuyMar 18, 2012
  3. Felipe TanusMar 18, 2012
  4. Thomas RastMar 21, 2012
  5. Felipe TanusMar 21, 2012

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.