linux-ext4.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Avantika Mathur <mathur@linux.vnet.ibm.com>
To: linux-ext4 <linux-ext4@vger.kernel.org>
Subject: Ext4 devel interlock meeting minutes (October 22, 2007)
Date: Tue, 23 Oct 2007 14:07:05 -0700	[thread overview]
Message-ID: <471E6279.2000603@linux.vnet.ibm.com> (raw)

Ext4 Developer Interlock Call
October 22, 2007: Meeting Minutes

Attendees: Mingming Cao, Andreas Dilger, Eric Sandeen, Dave Kleikamp, 
Jose Santos, Aneesh Veetil, Valerie Clement, Avantika Mathur

- There has been discussion on linux-ext4 about overflow in ext2 with 64 
KB block size.  Discussed adding an incompat flag to this feature and 
concluded that it is too late to do this; it will be treated as a bug fix.

Patch Status: patches that were not picked up to mainline in the recent 
pull:
- journal_checksum patches - the fsstress kernel oops is not yet 
resolved, Avantika will be working on this.
- i_version: Jean-Noel recently sent out an updated version which adds a 
lock every time i_version is updated.  Still waiting on more review
- mballoc - target for next kernel release. Remaining work:
    - Aneesh plans to run some performance test and include results in 
	the patch description.
    - Waiting for Alex to address the fixme's that aneesh has added to 
	the code, for more clarification.
- block groupdescriptor sync with e2fsprogs:
- Aneeesh recently posted patches which have been added to the patch queue.

E2fsprogs
- Ted has added new branches the the e2fsprogs git tree
    - master: current stable version
    - next: patches expected to go into the next stable version
    - pu: proposed update; patches that are in preliminary review and 
	test phase
- E2fsprogs patches should probably be submitted against the 'next' 
branch of the git tree.

- Aneesh was looking for patches to support mke2fs of large 
filesystems.  Valerie's old patches don't apply cleanly.

- Documentation in the kernel tree; ext4.txt is out of date and needs to 
be updated.

Performance:
- Andreas had asked Chris Mason to add ext4 to his BTRfs benchmarks. 
Chris Mason reported that ext4 is doing poorly on a test which performs 
kernel untar and compile on 20 kernels in a row.  The performance of 
ext4 on reads is poor compared to ext3.
- Eric will talk to Chris and get all of the details of the tests.
- Eric suggested enabling delalloc,mballoc mount options by default.  
The dellaloc option can then be disabled if the fs is not in writeback 
journaling mode.

             reply	other threads:[~2007-10-23 21:06 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-10-23 21:07 Avantika Mathur [this message]
2007-10-24 17:55 ` Ext4 devel interlock meeting minutes (October 22, 2007) Jan Kara

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=471E6279.2000603@linux.vnet.ibm.com \
    --to=mathur@linux.vnet.ibm.com \
    --cc=linux-ext4@vger.kernel.org \
    /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;
as well as URLs for NNTP newsgroup(s).