From: Daniel Phillips <phillips@bonn-fries.net>
To: Alexander Viro <viro@math.psu.edu>
Cc: linux-kernel@vger.kernel.org, ext2-devel@lists.sourceforge.net
Subject: Re: [PATCH] Son of Unbork (1 of 3)
Date: Sun, 24 Feb 2002 03:33:36 +0100 [thread overview]
Message-ID: <E16eoTq-0001GK-00@starship.berlin> (raw)
In-Reply-To: <Pine.GSO.4.21.0202251323160.3162-100000@weyl.math.psu.edu>
In-Reply-To: <Pine.GSO.4.21.0202251323160.3162-100000@weyl.math.psu.edu>
On February 25, 2002 07:28 pm, Alexander Viro wrote:
> On Sat, 23 Feb 2002, Daniel Phillips wrote:
> > Please tell me who wrote this:
> >
> > struct super_operations {
> > struct inode *(*alloc_inode)(struct super_block *sb);
> > void (*destroy_inode)(struct inode *)
>
> I had. With inodes it _does_ provide things that can't be done
> without these methods. Namely, common allocation of generic and
> fs-private part *on* *the* *fast* *path* *for* *class* *with*
> *many* *instances*.
>
> The latter parts are missing in case of superblocks. We don't
> allocate hundreds of thousands of superblocks. Moreover, ones
> allocated live much longer than normal struct inode.
>
> IOW, common allocation is worthless in this case and that's the
> only rationale for ->alloc_inode()/->destroy_inode().
You are being random. I'll leave the patch as it stands, I'm satisfied with
it. If you want to change it, go ahead, you have it in your mailbox. Tear
the whole thing up and rewrite it if you like. Just don't delay this
important work because of stupid personality issues.
--
Daniel
next prev parent reply other threads:[~2002-02-26 1:41 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-02-23 18:12 Daniel Phillips
2002-02-25 17:24 ` Alexander Viro
2002-02-23 18:30 ` Daniel Phillips
2002-02-25 17:34 ` Alexander Viro
2002-02-23 19:13 ` Daniel Phillips
2002-02-25 18:28 ` Alexander Viro
2002-02-24 2:33 ` Daniel Phillips [this message]
2002-02-25 17:37 ` Martin Dalecki
2002-02-25 17:57 ` Alan Cox
2002-02-25 17:45 ` Alexander Viro
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=E16eoTq-0001GK-00@starship.berlin \
--to=phillips@bonn-fries.net \
--cc=ext2-devel@lists.sourceforge.net \
--cc=linux-kernel@vger.kernel.org \
--cc=viro@math.psu.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®