From: Hans Reiser <reiser@namesys.com>
To: Mike Young <myoung@wildernessvoice.com>
Cc: 'darren' <teodarren@myrealbox.com>, reiserfs-list@namesys.com
Subject: Re: Object Oriented FS
Date: Mon, 27 Oct 2003 22:01:12 +0300 [thread overview]
Message-ID: <3F9D6B78.2090001@namesys.com> (raw)
In-Reply-To: <200310271843.KAA08513@amber.he.net>
Mike Young wrote:
>Hans,
>
>Do you believe this is just a marketing convention to refer to a file-system
>as an object oriented one?
>
No. Also, note that they aren't saying the fs is object oriented, they
are saying the storage system is not a block device but an object server.
> Bear in mind that Microsoft is supposed to
>enrich their NTFS with object support from SQL Server in their next OS.
>
Reiser4 and MS are talking about different layers than Panassas when we
talk about being object oriented. MS objects and Reiser4 plugins might
be similar notions, I am not an NTFS expert.....
> The
>code name for this is Longhorn.
>
>I really can't tell what this means to a file system in terms of support.
>It sounds like it's intended to provide support for really large numbers of
>files in a single directory
>
Uh, reiser4 does that without objects having anything to do with it.
Large numbers of files in a single directory means one should use trees
not linear searches.....
> vs. nested ones. But I'm just not sure. Do you
>see a limitation, going forward, with Reiser4 and large numbers of files?
>
>
We have trouble with more than 2^60 files in the filesystem.
;-)
An interesting question though is at how many files in a directory being
read does dcache start to croak and sys_reiser4 becomes a performance
necessity....? Maybe in a few weeks Mr. Demidov can measure that.
>Thanks,
>
>Mike
>
>-----Original Message-----
>From: Hans Reiser [mailto:reiser@namesys.com]
>Sent: Monday, October 27, 2003 10:23 AM
>To: darren
>Cc: reiserfs-list@namesys.com
>Subject: Re: Object Oriented FS
>
>darren wrote:
>
>
>
>>allows very high
>>throughput by scaling
>>
>>
>>
>>
>>
>>
>>
>Do you know what that means? (Seriously, I don't....)
>
>
>
--
Hans
next prev parent reply other threads:[~2003-10-27 19:01 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-10-27 3:46 ReiserFS v3 + millions of files? Dan Oglesby
2003-10-27 6:55 ` Hans Reiser
2003-10-27 9:38 ` Hans Reiser
2003-10-27 11:42 ` Nikita Danilov
2003-10-27 16:03 ` Object Oriented FS darren
2003-10-27 18:23 ` Hans Reiser
2003-10-27 18:43 ` Mike Young
2003-10-27 19:01 ` Hans Reiser [this message]
2003-10-27 18:56 ` Andreas Dilger
2003-10-28 1:40 ` Steven Cole
2003-10-28 4:46 ` lrc1
2003-10-29 6:03 ` ReiserFS v3 + millions of files? Todd Lyons
2003-10-29 8:44 ` Hans Reiser
2003-10-30 6:04 ` Todd Lyons
2003-10-30 7:33 ` Andreas Dilger
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=3F9D6B78.2090001@namesys.com \
--to=reiser@namesys.com \
--cc=myoung@wildernessvoice.com \
--cc=reiserfs-list@namesys.com \
--cc=teodarren@myrealbox.com \
/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.