Re: [Ext2-devel] [RFC][15/21]e2fsprogs modify variables for bitmap to exceed 2G

Hi, Ted

We could bump the major version number, but what I'd much rather do is
to create new functions which use the 64-bit blk64_t (i.e.,
ext2fs_mark_block_bitmap2).  This will make the patches much bigger,
but it allows us to preserve backwards compatibility.

I'm trying to add new functions which use the 64-bit block number in
e2fsprogs.  But I think the name "ext2fs_mark_blocks_bitmap2" is rather
obscure.  How about adding "_64" to the end of the name? (i.e. ext2fs_
mark_block_bitmap_64 for ext2fs_mark_block_bitmap)

Cheers, sho
-
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/

---

• References:
  • [RFC][15/21]e2fsprogs modify variables for bitmap to exceed 2G
    • From: [email protected]
  • Re: [Ext2-devel] [RFC][15/21]e2fsprogs modify variables for bitmap to exceed 2G
    • From: "Theodore Ts'o" <[email protected]>

• Prev by Date: Re: [Ext2-devel] Re: [RFC][PATCH 0/2]Extend ext3 filesystem limit from 8TB to 16TB
• Next by Date: Re: [PATCH 5/5] Swapless V2: Revise main migration logic
• Previous by thread: Re: [Ext2-devel] [RFC][15/21]e2fsprogs modify variables for bitmap to exceed 2G
• Next by thread: [RFC][16/21]e2fsprogs enlarge file size and filesystem size
• 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]