Re: TIMESPEC_TO_NSEC(), futex(2) & __thrsleep(2)

> On Dec 31, 2019, at 9:35 AM, Martin Pieuchot wrote: > > I'd like to stop converting the given timespec to ticks and instead use > nanoseconds. This is part of the ongoing effort to reduce the use of > `hz' through the kernel. > > Since I don't know C I'd appreciate any pointer about the check

Re: Add pcidev for Ryzen 3x ccp

On Wed, Jan 01, 2020 at 09:25:16PM -0500, Todd Mortimer wrote: > On Thu, Jan 02, 2020 at 09:33:59AM +1000, Jonathan Matthew wrote: > > On Thu, Jan 02, 2020 at 10:20:52AM +1100, Jonathan Gray wrote: > > > On Wed, Jan 01, 2020 at 11:21:45AM -0500, Todd Mortimer wrote: > > > > On Thu, Jan 02, 2020 at

Re: Add -R alias to -r for scp(1)

On Wed, Jan 01, 2020 at 09:31:29PM -0500, Kurt Mosiejczuk wrote: > On Wed, Jan 01, 2020 at 09:15:14PM -0500, Ted Unangst wrote: > > Kurt Mosiejczuk wrote: > > > cp(1) uses -R for recursive copy. scp(1) uses -r. This diff adds -R as an > > > alias for -r to scp(1) for those assuming consistency with

Re: Add -R alias to -r for scp(1)

On Wed, Jan 01, 2020 at 09:15:14PM -0500, Ted Unangst wrote: > Kurt Mosiejczuk wrote: > > cp(1) uses -R for recursive copy. scp(1) uses -r. This diff adds -R as an > > alias for -r to scp(1) for those assuming consistency with cp(1). > But it doesn't implement cp -R semantics. It does the copy the

Re: Add pcidev for Ryzen 3x ccp

On Thu, Jan 02, 2020 at 09:33:59AM +1000, Jonathan Matthew wrote: > On Thu, Jan 02, 2020 at 10:20:52AM +1100, Jonathan Gray wrote: > > On Wed, Jan 01, 2020 at 11:21:45AM -0500, Todd Mortimer wrote: > > > On Thu, Jan 02, 2020 at 02:41:11AM +1100, Jonathan Gray wrote: > > > > On Wed, Jan 01, 2020 at

Re: Add -R alias to -r for scp(1)

Kurt Mosiejczuk wrote: > cp(1) uses -R for recursive copy. scp(1) uses -r. This diff adds -R as an > alias for -r to scp(1) for those assuming consistency with cp(1). But it doesn't implement cp -R semantics. It does the copy the way cp -r does. (For symlinks, etc.)

Add -R alias to -r for scp(1)

cp(1) uses -R for recursive copy. scp(1) uses -r. This diff adds -R as an alias for -r to scp(1) for those assuming consistency with cp(1). --Kurt Index: scp.1 === RCS file: /cvs/src/usr.bin/ssh/scp.1,v retrieving revision 1.87 diff

Re: Add pcidev for Ryzen 3x ccp

On Thu, Jan 02, 2020 at 10:20:52AM +1100, Jonathan Gray wrote: > On Wed, Jan 01, 2020 at 11:21:45AM -0500, Todd Mortimer wrote: > > On Thu, Jan 02, 2020 at 02:41:11AM +1100, Jonathan Gray wrote: > > > On Wed, Jan 01, 2020 at 09:53:39AM -0500, Todd Mortimer wrote: > > > > My CPU has a CCP that isn't

Re: Add pcidev for Ryzen 3x ccp

On Wed, Jan 01, 2020 at 11:21:45AM -0500, Todd Mortimer wrote: > On Thu, Jan 02, 2020 at 02:41:11AM +1100, Jonathan Gray wrote: > > On Wed, Jan 01, 2020 at 09:53:39AM -0500, Todd Mortimer wrote: > > > My CPU has a CCP that isn't in the known list, so add it and tell ccp > > > about it. > > > > > >

Re: Add pcidev for Ryzen 3x ccp

On Thu, Jan 02, 2020 at 02:41:11AM +1100, Jonathan Gray wrote: > On Wed, Jan 01, 2020 at 09:53:39AM -0500, Todd Mortimer wrote: > > My CPU has a CCP that isn't in the known list, so add it and tell ccp > > about it. > > > > Tested on Ryzen 3900x. > > > > ok? > > > > Will commit a pcidevs regen

Re: Add pcidev for Ryzen 3x ccp

On Wed, Jan 01, 2020 at 09:53:39AM -0500, Todd Mortimer wrote: > My CPU has a CCP that isn't in the known list, so add it and tell ccp > about it. > > Tested on Ryzen 3900x. > > ok? > > Will commit a pcidevs regen immediately after. Are your cpu lines in dmesg 17-3* or 17-7*? Ryzen 3900x shoul

Re: uow(4) & tsleep

On Wed, Jan 01, 2020 at 03:32:09PM +0100, Martin Pieuchot wrote: > UOW_TIMEOUT is expressed in msec, so use MSEC_TO_NSEC() and tsleep_nsec(9) > instead of dereferencing `hz'. > > Ok? OK bluhm@ > Index: uow.c > === > RCS file: /cvs/sr

Re: ugen(4) and tsleep_nsec(9)

On Wed, Jan 01, 2020 at 03:22:30PM +0100, Martin Pieuchot wrote: > `sce' timeouts, like most of the USB timeouts are expressed in ms. So > use MSEC_TO_NSEC() and tsleep_nsec(9) accordingly. > > Ok? OK bluhm@ I prefer unique sleeping strings for easier debugging. Can we change that to "ugenrint"

Add pcidev for Ryzen 3x ccp

My CPU has a CCP that isn't in the known list, so add it and tell ccp about it. Tested on Ryzen 3900x. ok? Will commit a pcidevs regen immediately after. diff --git a/sys/dev/pci/ccp_pci.c b/sys/dev/pci/ccp_pci.c index 2259594644b..c8dcc8750fc 100644 --- a/sys/dev/pci/ccp_pci.c +++ b/sys/dev/

uow(4) & tsleep

UOW_TIMEOUT is expressed in msec, so use MSEC_TO_NSEC() and tsleep_nsec(9) instead of dereferencing `hz'. Ok? Index: uow.c === RCS file: /cvs/src/sys/dev/usb/uow.c,v retrieving revision 1.35 diff -u -p -r1.35 uow.c --- uow.c 6

ugen(4) and tsleep_nsec(9)

`sce' timeouts, like most of the USB timeouts are expressed in ms. So use MSEC_TO_NSEC() and tsleep_nsec(9) accordingly. Ok? Index: ugen.c === RCS file: /cvs/src/sys/dev/usb/ugen.c,v retrieving revision 1.100 diff -u -p -r1.100 ugen

Re: TIMESPEC_TO_NSEC(), futex(2) & __thrsleep(2)

On 31/12/19(Tue) 15:00, Todd C. Miller wrote: > On Tue, 31 Dec 2019 16:35:59 +0100, Martin Pieuchot wrote: > > > I'd like to stop converting the given timespec to ticks and instead use > > nanoseconds. This is part of the ongoing effort to reduce the use of > > `hz' through the kernel. > > > > Si

Re: TIMESPEC_TO_NSEC(), futex(2) & __thrsleep(2)

On 31/12/19(Tue) 17:44, Alexander Bluhm wrote: > On Tue, Dec 31, 2019 at 04:35:59PM +0100, Martin Pieuchot wrote: > > Since I don't know C I'd appreciate any pointer about the checks that > > should be added to TIMESPEC_TO_NSEC(). > > Perhaps this way? Thanks. > static inline uint64_t > TIMESPEC