On Sat, Jun 08, 2019 at 01:47:39PM +0200, Oliver Pinter wrote:
> On Saturday, June 8, 2019, Konstantin Belousov wrote:
>
> > On Sat, Jun 08, 2019 at 02:57:27AM +, Rick Macklem wrote:
> > > Hi,
> > >
> > > I've started working of a copy_file_range() syscall for FreeBSD. I think
> > I have the
On Sun, Jun 09, 2019 at 06:12:59AM +, Rick Macklem wrote:
> Konstantin Belousov wrote:
> >On Sat, Jun 08, 2019 at 02:57:27AM +, Rick Macklem wrote:
> >> Hi,
> >>
> First off, thanks Kostik for the fine explanation. I agree with Oliver that
> it should
> be captured somewhere like the wiki.
Konstantin Belousov wrote:
>On Sat, Jun 08, 2019 at 02:57:27AM +, Rick Macklem wrote:
>> Hi,
>>
First off, thanks Kostik for the fine explanation. I agree with Oliver that it
should
be captured somewhere like the wiki. I'm no wiki guy, so hopefully someone else
will do this?
>> I've started w
On Saturday, June 8, 2019, Konstantin Belousov wrote:
> On Sat, Jun 08, 2019 at 02:57:27AM +, Rick Macklem wrote:
> > Hi,
> >
> > I've started working of a copy_file_range() syscall for FreeBSD. I think
> I have the
> > kernel patched and ready for some testing.
> > However, I'm confused abou
On Sat, Jun 08, 2019 at 02:57:27AM +, Rick Macklem wrote:
> Hi,
>
> I've started working of a copy_file_range() syscall for FreeBSD. I think I
> have the
> kernel patched and ready for some testing.
> However, I'm confused about what I need to do in src/lib/libc/sys?
> - Some syscalls have li
Hi,
I've started working of a copy_file_range() syscall for FreeBSD. I think I have
the
kernel patched and ready for some testing.
However, I'm confused about what I need to do in src/lib/libc/sys?
- Some syscalls have little .c files, but other ones do not.
When is one of these little .c files
