Re: [PATCH v2] ioctl_getfsmap.2: document the GETFSMAP ioctl

On 05/18/2017 04:07 AM, Darrick J. Wong wrote: > Document the new GETFSMAP ioctl that returns the physical layout of a > (disk-based) filesystem. Thanks, Darrick! Applied (with a few minor edits). (Currently sitting in a local branch, just in case anyone sends review comments that need integrating

Re: [PATCH v2] fideduperange.2: fix the discussion of maximum sizes

On 11/23/2016 05:49 AM, Omar Sandoval wrote: > On Tue, Nov 22, 2016 at 08:48:16PM -0800, Darrick J. Wong wrote: >> Fix the discussion of the limitations on the dest_count and src_length >> parameters to the fideduperange ioctl to reflect what's actually in the >> kernel. >> >> Signed-off-by: Darric

Re: [PATCH v2] fideduperange.2: fix the discussion of maximum sizes

On 11/23/2016 05:48 AM, Darrick J. Wong wrote: > Fix the discussion of the limitations on the dest_count and src_length > parameters to the fideduperange ioctl to reflect what's actually in the > kernel. Thanks Darrick. Applied. Cheers, Michael > Signed-off-by: Darrick J. Wong > --- > man2/i

Re: [PATCH 2/2] man2/ioctl_fideduperange.2: clarify operation some more

Hi Darrick, On 10/18/2016 03:54 AM, Darrick J. Wong wrote: > Clarify the behavior of the dedupe ioctl. Thanks! Applied. Cheers, Michael > Signed-off-by: Darrick J. Wong > --- > man2/ioctl_ficlonerange.2 |2 +- > man2/ioctl_fideduperange.2 | 26 ++ > 2 files ch

Re: [PATCH 1/2] man2/fallocate.2: document behavior with shared blocks

Hi Darrick, On 10/18/2016 03:54 AM, Darrick J. Wong wrote: > Add a blurb to the fallocate manpage explaining that the fallocate > command with the UNSHARE mode flag may use CoW to unshare blocks to > guarantee that a disk write won't fail with ENOSPC. Thanks! Applied. Cheers, Michael > > Sig

Re: [PATCH 8/9] vfs: hoist the btrfs deduplication ioctl to the vfs

Hi Darrick, On 01/12/2016 08:14 PM, Darrick J. Wong wrote: [adding btrfs to the cc since we're talking about a whole new dedupe interface] In the discussion below, many points of possible improvement were notedfor the man page Would you be willing to put together a patch please? Thanks,

Re: [PATCH v2 10/9] copy_file_range.2: New page documenting copy_file_range()

Hi Anna, On 09/11/2015 10:30 PM, Anna Schumaker wrote: > copy_file_range() is a new system call for copying ranges of data > completely in the kernel. This gives filesystems an opportunity to > implement some kind of "copy acceleration", such as reflinks or > server-side-copy (in the case of NFS)

Re: Documenting MS_LAZYTIME

On 02/27/2015 06:51 PM, Darrick J. Wong wrote: > On Fri, Feb 27, 2015 at 09:01:10AM +0100, Michael Kerrisk (man-pages) wrote: >> On 02/27/2015 01:04 AM, Theodore Ts'o wrote: >>> On Thu, Feb 26, 2015 at 02:36:33PM +0100, Michael Kerrisk (man-pages) wrote: >>&g

Re: Documenting MS_LAZYTIME

Hello Omar, On 02/27/2015 09:08 AM, Omar Sandoval wrote: > On Fri, Feb 27, 2015 at 09:01:10AM +0100, Michael Kerrisk (man-pages) wrote: >> On 02/27/2015 01:04 AM, Theodore Ts'o wrote: >>> On Thu, Feb 26, 2015 at 02:36:33PM +0100, Michael Kerrisk (man-pages) wrote: >>

Re: Documenting MS_LAZYTIME

On 02/27/2015 01:04 AM, Theodore Ts'o wrote: > On Thu, Feb 26, 2015 at 02:36:33PM +0100, Michael Kerrisk (man-pages) wrote: >> >> The disadvantage of MS_STRICTATIME | MS_LAZYTIME is that >> in the case of a system crash, the atime and mtime fields >> on

Re: Documenting MS_LAZYTIME

On 02/26/2015 02:31 PM, Theodore Ts'o wrote: > On Thu, Feb 26, 2015 at 09:49:39AM +0100, Michael Kerrisk (man-pages) wrote: >>> How about somethign like "This mount significantly reduces writes >>> needed to update the inode's timestamps, especially mtime and a

Re: Documenting MS_LAZYTIME

On 02/23/2015 05:24 PM, Eric Sandeen wrote: > On 2/23/15 6:20 AM, Austin S Hemmelgarn wrote: >> On 2015-02-20 21:56, Theodore Ts'o wrote: >>> On Fri, Feb 20, 2015 at 09:49:34AM -0600, Eric Sandeen wrote: >This mount option significantly reduces writes to the >

Re: Documenting MS_LAZYTIME

Ted, On 02/21/2015 03:56 AM, Theodore Ts'o wrote: > On Fri, Feb 20, 2015 at 09:49:34AM -0600, Eric Sandeen wrote: >> >>> This mount option significantly reduces writes to the >>> inode table for workloads that perform frequent random >>> writes to pre

Re: Documenting MS_LAZYTIME

On 02/20/2015 04:49 PM, Eric Sandeen wrote: > On 2/20/15 2:50 AM, Michael Kerrisk wrote: >> Hello Ted, >> >> Based on your commit message 0ae45f63d4e, I I wrote the documentation >> below for MS_LAZYTIME, to go into the mount(2) man page. Could you >> please check it over and let me know if it's ac

Re: Documenting MS_LAZYTIME

On 20 February 2015 at 13:32, Andreas Dilger wrote: > On Feb 20, 2015, at 1:50 AM, Michael Kerrisk wrote: >> >> Hello Ted, >> >> Based on your commit message 0ae45f63d4e, I I wrote the documentation >> below for MS_LAZYTIME, to go into the mount(2) man page. Could you >> please check it over and