On Thu 11-04-13 17:29:39, Ramkumar Ramachandra wrote:
> Jan Kara wrote:
> > Initially, you will have to flip the flag on every directory in the
> > subtree. But the flag is persistently stored on disk so you have to do it
> > once when the directory is created and then each time you notice the
>
Jan Kara wrote:
> Initially, you will have to flip the flag on every directory in the
> subtree. But the flag is persistently stored on disk so you have to do it
> once when the directory is created and then each time you notice the
> directory has changed and the flag has been cleared.
How is
Jan Kara wrote:
Initially, you will have to flip the flag on every directory in the
subtree. But the flag is persistently stored on disk so you have to do it
once when the directory is created and then each time you notice the
directory has changed and the flag has been cleared.
How is this
On Thu 11-04-13 17:29:39, Ramkumar Ramachandra wrote:
Jan Kara wrote:
Initially, you will have to flip the flag on every directory in the
subtree. But the flag is persistently stored on disk so you have to do it
once when the directory is created and then each time you notice the
On Thu 11-04-13 00:06:02, Ramkumar Ramachandra wrote:
> [Dropping git people from the CC, as this is not relevant to git anymore]
>
> Okay, let me attempt to understand this.
>
> Jan Kara wrote:
> > On Fri 05-04-13 17:12:29, Al Viro wrote:
> >> On Fri, Apr 05, 2013 at 05:55:34PM +0200, Jan Kara
[Dropping git people from the CC, as this is not relevant to git anymore]
Okay, let me attempt to understand this.
Jan Kara wrote:
> On Fri 05-04-13 17:12:29, Al Viro wrote:
>> On Fri, Apr 05, 2013 at 05:55:34PM +0200, Jan Kara wrote:
>>
>> > What your question reminds me is an idea of recursive
[Dropping git people from the CC, as this is not relevant to git anymore]
Okay, let me attempt to understand this.
Jan Kara wrote:
On Fri 05-04-13 17:12:29, Al Viro wrote:
On Fri, Apr 05, 2013 at 05:55:34PM +0200, Jan Kara wrote:
What your question reminds me is an idea of recursive
On Thu 11-04-13 00:06:02, Ramkumar Ramachandra wrote:
[Dropping git people from the CC, as this is not relevant to git anymore]
Okay, let me attempt to understand this.
Jan Kara wrote:
On Fri 05-04-13 17:12:29, Al Viro wrote:
On Fri, Apr 05, 2013 at 05:55:34PM +0200, Jan Kara wrote:
On Fri 05-04-13 17:12:29, Al Viro wrote:
> On Fri, Apr 05, 2013 at 05:55:34PM +0200, Jan Kara wrote:
>
> > What your question reminds me is an idea of recursive modification time
> > stamp on directories. That is a time stamp that gets updated whenever
> > anything in the tree under the directory
On Fri 05-04-13 17:12:29, Al Viro wrote:
On Fri, Apr 05, 2013 at 05:55:34PM +0200, Jan Kara wrote:
What your question reminds me is an idea of recursive modification time
stamp on directories. That is a time stamp that gets updated whenever
anything in the tree under the directory
Jan Kara wrote:
> Hum, I have somewhat hard time to understand what do you mean by
> 'magically optimized syscalls'. What should happen in VFS to speedup your
> load?
In retrospect, I think this is a terrible hack to begin with. Tuning
the filesystem specifically for git repositories is
On Fri, Apr 05, 2013 at 05:55:34PM +0200, Jan Kara wrote:
> What your question reminds me is an idea of recursive modification time
> stamp on directories. That is a time stamp that gets updated whenever
> anything in the tree under the directory changes. Now this would be too
> expensive to
Hi,
On Mon 18-03-13 16:18:11, Ramkumar Ramachandra wrote:
> We, the Git folks, were wondering how to speed things up. In an
> strace of "git status" on linux-2.6.git, we found:
>
> top syscalls sorted top syscalls sorted
> by acc. timeby number
>
Hi,
On Mon 18-03-13 16:18:11, Ramkumar Ramachandra wrote:
We, the Git folks, were wondering how to speed things up. In an
strace of git status on linux-2.6.git, we found:
top syscalls sorted top syscalls sorted
by acc. timeby number
On Fri, Apr 05, 2013 at 05:55:34PM +0200, Jan Kara wrote:
What your question reminds me is an idea of recursive modification time
stamp on directories. That is a time stamp that gets updated whenever
anything in the tree under the directory changes. Now this would be too
expensive to maintain
Jan Kara wrote:
Hum, I have somewhat hard time to understand what do you mean by
'magically optimized syscalls'. What should happen in VFS to speedup your
load?
In retrospect, I think this is a terrible hack to begin with. Tuning
the filesystem specifically for git repositories is inelegant
16 matches
Mail list logo
