Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > linux.kernel > #1722329
| From | David Laight <David.Laight@ACULAB.COM> |
|---|---|
| Newsgroups | linux.kernel |
| Subject | RE: [PATCH v2 0/2] enable hires timer to timeout datagram socket |
| Date | 2017-08-29 13:20 +0200 |
| Message-ID | <ujMIO-1VL-3@gated-at.bofh.it> (permalink) |
| References | <uhryN-1AG-9@gated-at.bofh.it> <uhvCq-4iI-15@gated-at.bofh.it> <ujcFk-4iC-13@gated-at.bofh.it> |
| Organization | linux.* mail to news gateway |
From: Vallish Vaidyeshwara
> Sent: 27 August 2017 21:47
...
> I respect the decision not to upstream this patch series, however I
> wanted to provide additional details. Application wanting high
> resolution events with real guarantees is not the case, but the case
> here is regression in system call behavior:
>
> 1) Change in system call behavior:
> strace from 4.4 test run of waiting for 180 seconds on datagram socket:
> 10:25:48.239685 setsockopt(3, SOL_SOCKET, SO_RCVTIMEO, "\264\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0", 16) = 0
> 10:25:48.239755 recvmsg(3, 0x7ffd0a3beec0, 0) = -1 EAGAIN (Resource temporarily unavailable)
> 10:28:48.236989 fstat(1, {st_mode=S_IFCHR|0620, st_rdev=makedev(136, 0), ...}) = 0
IMHO you should be complaining to the main kernel group who 'broke' the
timer code, not the networking group.
David
Back to linux.kernel | Previous | Next — Previous in thread | Find similar | Unroll thread
Re: [PATCH v2 0/2] enable hires timer to timeout datagram socket Vallish Vaidyeshwara <vallish@amazon.com> - 2017-08-27 22:50 +0200 RE: [PATCH v2 0/2] enable hires timer to timeout datagram socket David Laight <David.Laight@ACULAB.COM> - 2017-08-29 13:20 +0200
csiph-web