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

Re: [PATCH 1/2] Use git_open_noatime when accessing pack data

From
Jonathan Nieder <jrnieder@gmail.com>
Date
Nov 4, 2010, 05:04 UTC
Message-ID
<20101104050437.GB15018@burratino>
In-Reply-To
<7vvd4ew687.fsf@alter.siamese.dyndns.org>
Junio C Hamano wrote:
> Jonathan Nieder <jrnieder@gmail.com> writes:
Show 5 quoted lines
>> Judging from these three use cases, readonly open()s to the worktree
>> should indeed use noatime, but open()s of .git/config, say, should
>> not.  Hmm.
>
> Why not, when you are talking about readonly open?

A .git/config frequently accessed by git is being used, so tmpwatch shouldn't delete it. (Meanwhile, a worktree frequently accessed by git is not precious on that account, and letting git touch the atime there might mask more useful information about when other programs touched the files.)

But that is all very fuzzy to me. I tend to mount noatime except on /usr (for popularity-contest).

I guess I should put it another way. What if anything does readonly have to do with O_NOATIME? Why shouldn't we always use O_NOATIME? Why should the operating system provide atime at all?

Previous: Junio C HamanoNext: Kevin Ballard
Message 6 of 11 in “Work around too many file descriptors”
  1. 0/2 Work around too many file descriptorsShawn O. Pearce, Nov 1, 2010
  2. 1/2 Use git_open_noatime when accessing pack dataShawn O. Pearce, Nov 1, 2010
  3. Junio C HamanoNov 3, 2010
  4. Jonathan NiederNov 3, 2010
  5. Junio C HamanoNov 3, 2010
  6. Jonathan NiederNov 4, 2010
  7. Kevin BallardNov 4, 2010
  8. Junio C HamanoNov 5, 2010
  9. 2/2 Work around EMFILE when there are too many pack filesShawn O. Pearce, Nov 1, 2010
  10. Johannes SixtNov 2, 2010
  11. Junio C HamanoNov 3, 2010

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.