From: Kevin Ballard <kevin@sb.org>
To: Jonathan Nieder <jrnieder@gmail.com>
Cc: Junio C Hamano <gitster@pobox.com>,
"Shawn O. Pearce" <spearce@spearce.org>,
git@vger.kernel.org
Subject: Re: [PATCH 1/2] Use git_open_noatime when accessing pack data
Date: Wed, 3 Nov 2010 22:23:26 -0700 [thread overview]
Message-ID: <95C8862A-11A8-436C-AAD9-C231DA2BC3E4@sb.org> (raw)
In-Reply-To: <20101104050437.GB15018@burratino>
On Nov 3, 2010, at 10:04 PM, Jonathan Nieder wrote:
> 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?
atime is useful for user-level files that are opened or modified as a
direct result of actions the user took. I don't think a took like git
has any reason to ever want to touch atime.
-Kevin Ballard
next prev parent reply other threads:[~2010-11-04 5:23 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-11-01 22:54 [PATCH 0/2] Work around too many file descriptors Shawn O. Pearce
2010-11-01 22:54 ` [PATCH 1/2] Use git_open_noatime when accessing pack data Shawn O. Pearce
2010-11-03 17:07 ` Junio C Hamano
2010-11-03 17:41 ` Jonathan Nieder
2010-11-03 19:35 ` Junio C Hamano
2010-11-04 5:04 ` Jonathan Nieder
2010-11-04 5:23 ` Kevin Ballard [this message]
2010-11-05 17:26 ` Junio C Hamano
2010-11-01 22:54 ` [PATCH 2/2] Work around EMFILE when there are too many pack files Shawn O. Pearce
2010-11-02 8:44 ` Johannes Sixt
2010-11-03 17:06 ` Junio C Hamano
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
List information: http://vger.kernel.org/majordomo-info.html
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=95C8862A-11A8-436C-AAD9-C231DA2BC3E4@sb.org \
--to=kevin@sb.org \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=jrnieder@gmail.com \
--cc=spearce@spearce.org \
/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.
Code repositories for project(s) associated with this public inbox
https://80x24.org/mirrors/git.git
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).