Re: [RFC 8/8] Reduce inode memory usage for systems with a high MAX_NUMNODES

On 1/15/07, Christoph Lameter <[email protected]> wrote:

This solution may be a bit hokey. I tried other approaches but this
one seemed to be the simplest with the least complications. Maybe someone
else can come up with a better solution?

How about a 64-bit field in struct inode that's used as a bitmask if
there are no more than 64 nodes, and a pointer to a bitmask if there
are more than 64 nodes. The filesystems wouldn't need to be involved
then, as the bitmap allocation could be done in the generic code.

Paul
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [email protected]
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

---

• Follow-Ups:
  • Re: [RFC 8/8] Reduce inode memory usage for systems with a high MAX_NUMNODES
    • From: Christoph Lameter <[email protected]>

• References:
  • [RFC 0/8] Cpuset aware writeback
    • From: Christoph Lameter <[email protected]>
  • [RFC 8/8] Reduce inode memory usage for systems with a high MAX_NUMNODES
    • From: Christoph Lameter <[email protected]>

• Prev by Date: [PATCH -MM] e1000: update new hardware init layer code with bugfixes
• Next by Date: Re: data corruption with nvidia chipsets and IDE/SATA drives (k8 cpu errata needed?)
• Previous by thread: [RFC 8/8] Reduce inode memory usage for systems with a high MAX_NUMNODES
• Next by thread: Re: [RFC 8/8] Reduce inode memory usage for systems with a high MAX_NUMNODES
• Index(es):
  • Date
  • Thread

[Index of Archives]     [Kernel Newbies]     [Netfilter]     [Bugtraq]     [Photo]     [Stuff]     [Gimp]     [Yosemite News]     [MIPS Linux]     [ARM Linux]     [Linux Security]     [Linux RAID]     [Video 4 Linux]     [Linux for the blind]     [Linux Resources]