Hi David,
Thanks for the patch, I'll review it but likely it's fine. It will make it
to 5.1.1. As for setting maxsegs to 1, that patch could simply say we
don't allow maxsegs to be set below say 8 or whatever number you think
would avoid the problem.
Andy
On Mon, 22 Feb 2021, David Smith wrote:
> If somebody sets the max outstanding operations per request to 1 (xrootd.async maxsegs 1), reads will still usually fail with an error; this is the case before this patch too. I don't now if it's wanted to make a (probably) larger patch to cover that case; I leave this is it is for now.
>
> --
> You are receiving this because you are subscribed to this thread.
> Reply to this email directly or view it on GitHub:
> https://github.com/xrootd/xrootd/pull/1408#issuecomment-783571813
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub, or unsubscribe.
[
{
"@context": "http://schema.org",
"@type": "EmailMessage",
"potentialAction": {
"@type": "ViewAction",
"target": "https://github.com/xrootd/xrootd/pull/1408#issuecomment-783627302",
"url": "https://github.com/xrootd/xrootd/pull/1408#issuecomment-783627302",
"name": "View Pull Request"
},
"description": "View this Pull Request on GitHub",
"publisher": {
"@type": "Organization",
"name": "GitHub",
"url": "https://github.com"
}
}
]
Use REPLY-ALL to reply to list
To unsubscribe from the XROOTD-DEV list, click the following link:
https://listserv.slac.stanford.edu/cgi-bin/wa?SUBED1=XROOTD-DEV&A=1