From: Pavel Machek <pavel@ucw.cz>
To: Denis Vlasenko <vda@port.imtp.ilyichevsk.odessa.ua>
Cc: Keith Owens <kaos@ocs.com.au>, linux-kernel@vger.kernel.org
Subject: Re: [prepatch] address_space-based writeback
Date: Fri, 3 May 2002 09:56:34 +0200 [thread overview]
Message-ID: <20020503075634.GA232@elf.ucw.cz> (raw)
In-Reply-To: <9595.1020174038@ocs3.intra.ocs.com.au> <200205011416.g41EFnX04718@Port.imtp.ilyichevsk.odessa.ua>
Hi!
> I'll repeat myself. What if some advanced fs has no sensible way of
> generating inode? Does it have to 'fake' it, just like [v]fat does it now?
> (Yes, vfat is not 'advanced' fs, let's not discuss it...)
>
> The fact that minix,ext[23],etc has inode #s is an *implementation detail*.
> Historically entrenched in Unix.
>
> Bad:
> inum_a = inode_num(file1);
> inum_b = inode_num(file2);
> if(inum_a == inum_b) { same_file(); }
>
> Better:
> if(is_hardlinked(file1,file2) { same_file(); }
>
> Yes, new syscal, blah, blah, blah... Not worth the effort, etc...
> lets start a flamewar...
Its worse: You have 1000 files with same size, how do you find which
are hardlinked? With inode_num() it is hashtable, doable with
O(n). With syscall we are talking O(n^2).
Pavel
--
(about SSSCA) "I don't say this lightly. However, I really think that the U.S.
no longer is classifiable as a democracy, but rather as a plutocracy." --hpa
next prev parent reply other threads:[~2002-05-03 8:20 UTC|newest]
Thread overview: 48+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-04-10 11:21 [prepatch] address_space-based writeback Andrew Morton
2002-04-10 11:34 ` Alexander Viro
2002-04-10 19:16 ` Andrew Morton
2002-04-10 20:53 ` Alexander Viro
2002-04-10 22:12 ` Jan Harkes
2002-04-10 21:44 ` Andrew Morton
2002-04-10 22:56 ` Anton Altaparmakov
2002-04-10 22:31 ` Andrew Morton
2002-04-11 20:20 ` Linus Torvalds
2002-04-11 20:41 ` Alexander Viro
2002-04-11 21:27 ` Andrew Morton
2002-04-11 22:55 ` Andreas Dilger
2002-04-11 22:49 ` Andrew Morton
2002-04-12 0:12 ` Linus Torvalds
2002-04-11 23:10 ` Christoph Hellwig
2002-04-11 23:22 ` Anton Altaparmakov
2002-04-11 23:03 ` Andrew Morton
2002-04-12 4:19 ` Bill Davidsen
2002-04-12 1:15 ` Anton Altaparmakov
2002-04-12 1:37 ` Linus Torvalds
2002-04-12 7:57 ` Anton Altaparmakov
2002-04-27 15:53 ` Jan Harkes
2002-04-28 3:03 ` Anton Altaparmakov
2002-04-29 9:03 ` Nikita Danilov
2002-04-29 11:11 ` Anton Altaparmakov
2002-04-29 11:59 ` Nikita Danilov
2002-04-29 12:34 ` Anton Altaparmakov
2002-04-29 13:01 ` Christoph Hellwig
2002-04-30 17:19 ` Denis Vlasenko
2002-04-30 13:15 ` john slee
2002-04-30 13:24 ` Billy O'Connor
2002-04-30 13:36 ` jlnance
2002-04-30 13:40 ` Keith Owens
2002-05-01 19:18 ` Denis Vlasenko
2002-05-02 8:49 ` Anton Altaparmakov
2002-05-03 15:35 ` Denis Vlasenko
2002-05-03 12:49 ` Helge Hafting
2002-05-03 22:47 ` Denis Vlasenko
2002-05-03 21:50 ` Anton Altaparmakov
2002-05-05 0:46 ` Denis Vlasenko
2002-05-03 7:56 ` Pavel Machek [this message]
2002-05-03 14:48 ` Rob Landley
2002-05-05 0:42 ` Denis Vlasenko
2002-04-30 16:12 ` Peter Wächtler
2002-04-10 23:02 ` Jan Harkes
2002-04-10 19:29 ` Jeremy Jackson
2002-04-10 19:41 ` Andrew Morton
2002-04-15 8:47 ` Andrew Morton
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=20020503075634.GA232@elf.ucw.cz \
--to=pavel@ucw.cz \
--cc=kaos@ocs.com.au \
--cc=linux-kernel@vger.kernel.org \
--cc=vda@port.imtp.ilyichevsk.odessa.ua \
/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.