| lists.openwall.net | lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC | |
|
Open Source and information security mailing list archives
| ||
|
Message-Id: <D5446EEA-D3AF-43BB-B862-6C9A741B0DC9@gmail.com> Date: Wed, 25 Jan 2012 11:06:29 -0700 From: Andreas Dilger <aedilger@...il.com> To: Eric Sandeen <sandeen@...hat.com> Cc: Amit Sahrawat <amit.sahrawat83@...il.com>, "xfs@....sgi.com" <xfs@....sgi.com>, "linux-ext4@...r.kernel.org" <linux-ext4@...r.kernel.org>, "linux-fsdevel@...r.kernel.org" <linux-fsdevel@...r.kernel.org>, LKML <linux-kernel@...r.kernel.org>, ChristophHellwig <hch@...radead.org>, Dave Chinner <david@...morbit.com> Subject: Re: Does Ext4 support parallel write similar to XFS? On 2012-01-25, at 9:34, Eric Sandeen <sandeen@...hat.com> wrote: > On 1/24/12 11:19 PM, Amit Sahrawat wrote: >> In XFS we can write parallel (i.,e we can make use of allocation >> groups for writing process). If the files are kept in individual >> directories, there is a possibility that first the blocks for that >> files be used from individual allocation groups. If I start ‘4’ >> writing process(cp 100MB_file /<dirnum>/) – after writing is finished >> – if I check the bmap – it does shows that initial allocation was from >> individual allocation groups. >> Even though in Ext4 also we do have groups – but I am not able to get >> behavior similar to XFS. >> If I check the file extents – the extents are in mixed form, the >> allocation pattern is also very fragmented. >> >> Please share more on this. Also, if there is a possible exact test >> case to check for parallel writes support. > > It seems that you are asking more about allocation policy than parallelism > in general? With either filesystem, you could use preallocation to wind > up with more contiguous files when you write them in parallel, though > that requires some idea of the file size ahead of time. > > ext4 doesn't have that exact dir::group heuristic that xfs uses, > but it does have other mechanisms and heuristics to try to get good > file and directory layout. > > In general, ext4 tries to put new root directories into new groups, see > comments above find_group_orlov(). Other directories tend to stay near > their parent directory. So it's really the roots of dir trees that > get spread across the disk in general. New non-dir inodes also tend to > stay close to their parent. (I think I have that all right ...) Note that this policy of new subdirectory placement (and indirectly the placement of files created therein) can be tuned by userspace by setting the "topdir" flag via setattr on the parent directory. This will push new subdirs created in that dir to a new group, which would In turn allow the files to allocate from that group. It is intended to be set on directories like /home where files within the subdirs are unrelated. Whether that is enough for your usage is unclear. > The test you describe above does result in more contiguous allocation on > xfs than on ext4, though - a quick check on kernel 3.2 yielded 2-3 > extents per file on ext4, 1 extent per file for xfs. > > -Eric > >> Thanks & Regards, >> Amit Sahrawat >> -- >> To unsubscribe from this list: send the line "unsubscribe linux-ext4" in >> the body of a message to majordomo@...r.kernel.org >> More majordomo info at http://vger.kernel.org/majordomo-info.html > > -- > To unsubscribe from this list: send the line "unsubscribe linux-ext4" in > the body of a message to majordomo@...r.kernel.org > More majordomo info at http://vger.kernel.org/majordomo-info.html -- To unsubscribe from this list: send the line "unsubscribe linux-ext4" in the body of a message to majordomo@...r.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
Powered by blists - more mailing lists