Re: copy_file_range is now a Linux kernel call

Hi,

On 2018-01-02 23:08:05 -0500, Tom Lane wrote:
> Andres Freund <andres(at)anarazel(dot)de> writes:
> > On 2018-01-02 22:44:04 -0500, Tom Lane wrote:
> > something like rwnd_copy_file_range or such.

> Bleah --- "rwnd" is unpronounceable and not an abbreviation we're
> currently using anywhere. If we go that way, let's brave carpal tunnel
> syndrome by calling it "rewind_copy_file_range". But I'm not that
> happy with any of these.

rewind_copy_file_range works for me.

> Filipe Rosset pointed out to me off-list that we're not the only
> ones feeling the pain:
>
> https://sourceforge.net/p/e2fsprogs/code/ci/01551bdba16ab16512a01affe02ade32c41ede8a
>
> Maybe go with copy_file_chunk like e2fsprogs did?

-0.2 - don't think it hurts to signal this isn't a general function.

Greetings,

Andres Freund