Re: Memory transaction instructions

2023-01-18 Thread Nicholas Piggin
On Wed Jan 18, 2023 at 7:05 PM AEST, David Howells wrote: > Linus Torvalds wrote: > > > And for the kernel, where we don't have bad locking, and where we > > actually use fine-grained locks that are _near_ the data that we are > > locking (the lockref of the dcache is obviously one example of that

Re: Memory transaction instructions

2023-01-18 Thread David Howells
Linus Torvalds wrote: > And for the kernel, where we don't have bad locking, and where we > actually use fine-grained locks that are _near_ the data that we are > locking (the lockref of the dcache is obviously one example of that, > but the skbuff queue you mention is almost certainly exactly th

Re: Memory transaction instructions

2023-01-16 Thread Linus Torvalds
On Mon, Jan 16, 2023 at 6:08 AM David Howells wrote: > > I'm not sure how relevant it is to the topic, but I seem to remember you > having a go at implementing spinlocks with x86_64 memory transaction > instructions a while back. Do you have any thoughts on whether these > i

Re: Memory transaction instructions

2023-01-16 Thread Matthew Wilcox
On Mon, Jan 16, 2023 at 02:08:15PM +, David Howells wrote: > Hi Linus, > > I'm not sure how relevant it is to the topic, but I seem to remember you > having a go at implementing spinlocks with x86_64 memory transaction > instructions a while back. Do you have any thoug

Memory transaction instructions

2023-01-16 Thread David Howells
Hi Linus, I'm not sure how relevant it is to the topic, but I seem to remember you having a go at implementing spinlocks with x86_64 memory transaction instructions a while back. Do you have any thoughts on whether these instructions are ever likely to become something we can use? I was lo