Re: liburing: expose syscalls?

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On 02/02/2020 01:51, Jens Axboe wrote:
>>> So you just want to have them exposed? I'd be fine with that. I'll
>>> take a patch :-)
>>>
>>
>> Depends on how it's used, but I'd strive to inline
>> __sys_io_uring_enter() to remove the extra indirect call into the
>> shared lib. Though, not sure about packaging and all this stuff. May
>> be useful to do that for liburing as well.
> 
> Not sure that actually matters when you're doing a syscall anyway, that
> should be the long pole for the operation.
> 

Yeah, but they are starting to stack up (+syscall() from glibc) and can became
even more layered on the user side.

-- 
Pavel Begunkov

Attachment: signature.asc
Description: OpenPGP digital signature


[Index of Archives]     [Linux Samsung SoC]     [Linux Rockchip SoC]     [Linux Actions SoC]     [Linux for Synopsys ARC Processors]     [Linux NFS]     [Linux NILFS]     [Linux USB Devel]     [Video for Linux]     [Linux Audio Users]     [Yosemite News]     [Linux Kernel]     [Linux SCSI]


  Powered by Linux