All of lore.kernel.org
 help / color / mirror / Atom feed
From: Rogier Wolff <R.E.Wolff@BitWizard.nl>
To: Rogier Wolff <R.E.Wolff@BitWizard.nl>
Cc: Larry McVoy <lm@work.bitmover.com>,
	Jeff Garzik <jgarzik@pobox.com>, Walter Landry <wlandry@ucsd.edu>,
	linux-kernel@vger.kernel.org
Subject: Re: A simple request (was Re: boring BK stats)
Date: Fri, 11 Oct 2002 16:14:54 +0200	[thread overview]
Message-ID: <20021011161454.C345@bitwizard.nl> (raw)
In-Reply-To: <20021011160828.B345@bitwizard.nl>

On Fri, Oct 11, 2002 at 04:08:28PM +0200, Rogier Wolff wrote:
> Jeff: 
> 
> The trick is that I would have hardlinked trees. Thus 
> 
> 	linux-2.2.18.clean/drivers/char/tty_ioctl.c
> and
> 	linux-2.2.18.rio/drivers/char/tty_ioctl.c
> 
> would have the same inode number, and diff wouldn't even bother to
> open the file.... 

FYI: 

Just tested the how long it takes to make a diff between my
2.2.18-clean tree and the 2.2.18.rio tree:

cold cache over NFS:     25 seconds
warm cache over NFS:     13 seconds
warm cache LOCAL disk:    0.34 seconds. 

					Roger. 

-- 
** R.E.Wolff@BitWizard.nl ** http://www.BitWizard.nl/ ** +31-15-2600998 **
*-- BitWizard writes Linux device drivers for any device you may have! --*
* The Worlds Ecosystem is a stable system. Stable systems may experience *
* excursions from the stable situation. We are currenly in such an       * 
* excursion: The stable situation does not include humans. ***************

  reply	other threads:[~2002-10-11 14:09 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-10-09 23:39 A simple request (was Re: boring BK stats) Walter Landry
2002-10-10 14:14 ` Jeff Garzik
2002-10-10 14:28   ` Larry McVoy
2002-10-10 14:40     ` Jeff Garzik
2002-10-10 15:32     ` Theodore Ts'o
2002-10-11 13:35     ` Rogier Wolff
2002-10-11 14:08       ` Rogier Wolff
2002-10-11 14:14         ` Rogier Wolff [this message]
2002-10-10 22:51   ` A simple request Walter Landry

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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20021011161454.C345@bitwizard.nl \
    --to=r.e.wolff@bitwizard.nl \
    --cc=jgarzik@pobox.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=lm@work.bitmover.com \
    --cc=wlandry@ucsd.edu \
    /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.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.