From: Johannes Schindelin <Johannes.Schindelin@gmx.de>
To: Geoffrey Irving <irving@naml.us>
Cc: "git@vger.kernel.org" <git@vger.kernel.org>
Subject: Re: [PATCH] Adding a cache of commit to patch-id pairs to speed up git-cherry
Date: Mon, 2 Jun 2008 19:22:01 +0100 (BST) [thread overview]
Message-ID: <alpine.DEB.1.00.0806021918590.13507@racer.site.net> (raw)
In-Reply-To: <7f9d599f0806021023r64affb36ne491792a962d455c@mail.gmail.com>
Hi,
On Mon, 2 Jun 2008, Geoffrey Irving wrote:
> On Mon, Jun 2, 2008 at 7:50 AM, Geoffrey Irving <irving@naml.us> wrote:
>
> I'll switch to mmapping.
>
> The git_mmap function in compat/mmap.c dies if NO_MMAP is defined and
> the map isn't MAP_PRIVATE. If I want to write an entry, will the memory
> be automatically updated if I write directly to the file descriptor (I
> haven't used mmap before)?
I think that you should only mmap() with MAP_PRIVATE, because you can
corrupt the data easily when a write failure is not handled properly.
So I'd suggest mmap() for reading, and writing to a locked file (I think
you did that already).
Ciao,
Dscho
prev parent reply other threads:[~2008-06-02 18:24 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-06-02 3:54 [PATCH] Adding a cache of commit to patch-id pairs to speed up git-cherry Geoffrey Irving
2008-06-02 6:13 ` Johannes Schindelin
2008-06-02 6:42 ` Jeff King
2008-06-02 14:35 ` Geoffrey Irving
2008-06-02 15:37 ` Johannes Schindelin
2008-06-02 15:49 ` Geoffrey Irving
2008-06-02 15:56 ` Shawn O. Pearce
2008-06-02 16:18 ` Johannes Schindelin
2008-06-02 16:26 ` Geoffrey Irving
2008-06-02 18:15 ` Johannes Schindelin
2008-06-07 23:50 ` Geoffrey Irving
2008-06-08 16:10 ` Johannes Schindelin
2008-06-02 14:50 ` Geoffrey Irving
2008-06-02 15:52 ` Johannes Schindelin
2008-06-02 17:23 ` Geoffrey Irving
2008-06-02 18:22 ` Johannes Schindelin [this message]
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=alpine.DEB.1.00.0806021918590.13507@racer.site.net \
--to=johannes.schindelin@gmx.de \
--cc=git@vger.kernel.org \
--cc=irving@naml.us \
/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).