JiaLong-Kang comments

Results 8 comments of


                                            JiaLong-Kang

Hello, why doesn't libnfs4 expose the access_deny parameter?

I did a full text search in the master branch and did not find the access_deny parameter. Which branch are you referring to?

Hello, why doesn't libnfs4 expose the access_deny parameter?

The author may think that byte range-based locks can maximize concurrent access, this is my guess.

Hello, why doesn't libnfs4 expose the access_deny parameter?

> The bye-range is an advisory lock, while the shared reservation is a mandatory lock. thank you for reminding me

When calling nfs_read or nfs_write and passing in a `count` that is too large, the `count` value is quietly changed

What you said makes sense, but this also brings up a problem: the application cannot be concurrent, which will also cause performance problems. The application needs to encapsulate read and...

When calling nfs_read or nfs_write and passing in a `count` that is too large, the `count` value is quietly changed

Thank you

When calling nfs_read or nfs_write and passing in a `count` that is too large, the `count` value is quietly changed

Okay, I'll try it over the weekend and let you know the result.

When calling nfs_read or nfs_write and passing in a `count` that is too large, the `count` value is quietly changed

I tested nfs_read and nfs_pread with large IO and they are ok. Thank you.

When calling nfs_read or nfs_write and passing in a `count` that is too large, the `count` value is quietly changed

I would like to ask whether the subsequent 'write' function will support large IO