Linux LVM users
 help / color / mirror / Atom feed
From: Dale Kemp <dale@inet.net.nz>
To: Andi Kleen <ak@suse.de>
Cc: Linux LVM <linux-lvm@msede.com>
Subject: Re: [linux-lvm] Re: IBM to release LVM Technology to the Linux
Date: Tue, 27 Jun 2000 14:22:55 +1200	[thread overview]
Message-ID: <39580FFF.42AD815D@inet.net.nz> (raw)
In-Reply-To: 20000627040212.A11246@gruyere.muc.suse.de

> The generic VFS code just never looks into the union,it is certainly
> abstractly used. Putting it into the union is just an performance optimization
> to make it use one allocation less in critical paths. File systems that
> do not want to change the source files are free to use the generic_ip
> pointer instead and let it point to a private structure.
>
> -Andi (who prefers Linux VFS over ``8.3 macro hell'' Sun/BSD derived VFS)

Yes, I see its abstractly used I guess OO programmers don't like the
whole concept of the union data structure, but for kernel programming,
device drivers etc it can make things go a bit quicker, and save space.

I hear from Andreas that design work is currently going on for VFS for
kernels 2.5/2.6. That's one of those things about Linux if it doesn't
exist, or needs improving, it's probably already being worked on -
relentless improvement.

-- Dale.

  reply	other threads:[~2000-06-27  2:22 UTC|newest]

Thread overview: 36+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2000-06-26 14:27 [linux-lvm] Re: IBM to release LVM Technology to the Linux Wilson, Eric
2000-06-26 23:18 ` Dale Kemp
2000-06-27  2:02   ` Andi Kleen
2000-06-27  2:22     ` Dale Kemp [this message]
2000-06-27  2:13   ` Andreas Dilger
  -- strict thread matches above, loose matches on Subject: below --
2000-06-30 20:50 benr
2000-06-30 20:28 benr
2000-06-30 20:53 ` Ragnar Kjørstad
2000-06-30 19:27 benr
2000-06-30 21:30 ` Dale Kemp
2000-06-30 23:05   ` Jens Benecke
2000-06-29 23:39 benr
2000-06-30  4:09 ` Dale Kemp
2000-06-30  9:34 ` Jan Niehusmann
2000-06-30 15:28 ` Ragnar Kjørstad
2000-06-29  5:32 Jean-Eric Cuendet
2000-06-29 10:49 ` Andi Kleen
2000-06-29  1:23 benr
2000-06-29 14:37 ` Ragnar Kjørstad
2000-06-26 21:44 benr
2000-06-27  3:53 ` Paul Jakma
2000-06-26 20:59 benr
2000-06-23 21:04 benr
2000-06-23 23:49 ` Paul Jakma
2000-06-24  6:37   ` Dale Kemp
2000-06-24 18:07     ` S. Ryan Quick
2000-06-25  1:25       ` Dale Kemp
2000-06-26  6:31     ` Martin K. Petersen
2000-06-23 12:52 hpuxadm
2000-06-23 15:20 ` Jens Benecke
2000-06-22 19:37 benr
2000-06-23  1:23 ` Dale Kemp
2000-06-23 20:55 ` Martin K. Petersen
2000-06-21 22:27 benr
     [not found] <85256900.007B81E0.00@d54mta02.raleigh.ibm.com>
2000-06-18 22:51 ` Andreas Dilger
2000-06-21 17:28   ` Martin K. Petersen

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=39580FFF.42AD815D@inet.net.nz \
    --to=dale@inet.net.nz \
    --cc=ak@suse.de \
    --cc=linux-lvm@msede.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox