Project

General

Profile

Actions
Copy link

Tasks #4500

open

Identify fields in CDentry which aren't permanently necessary

Added by Greg Farnum about 11 years ago. Updated almost 8 years ago.

Status:
New
Priority:
Normal
Assignee:
-
Category:
Performance/Resource Usage
Target version:
-
% Done:

0%

Tags:
Reviewed:
Affected Versions:
Component(FS):
MDS
Labels (FS):
Pull request ID:

Description

CDentry is in far better shape than CInode in this regard, but audit it for things which we don't always need in memory. If there are any, group them, rank them by memory saved, and create tasks to implement each.

Any groups we create should probably themselves use boost::pools.

Actions
Copy link
 #1

Updated by Greg Farnum about 11 years ago

  • Description updated (diff)
Actions
Copy link
 #2

Updated by Greg Farnum about 11 years ago

  • Subject changed from Identify fields in CInode which aren't permanently necessary to Identify fields in CDentry which aren't permanently necessary
Actions
Copy link
 #3

Updated by Greg Farnum almost 8 years ago

  • Category changed from 47 to Performance/Resource Usage
  • Component(FS) MDS added
Actions
Copy link

Also available in: Atom PDF