Re: bcachefs status update (it's done cooking; let's get this sucker merged)

2019-07-03 Thread Stefan K
Hello, is there a chance to get this in Kernel 5.3? And thanks for this fs! On Monday, June 10, 2019 9:14:08 PM CEST Kent Overstreet wrote: > Last status update: https://lkml.org/lkml/2018/12/2/46 > > Current status - I'm pretty much running out of things to polish and excuses > to > keep

Re: bcachefs status update (it's done cooking; let's get this sucker merged)

2019-06-29 Thread Luke Kenneth Casson Leighton
hey linus, you made news again, all blown up and pointless again. you're doing great: you're being honest. remember the offer i made to put you in touch with my friend. anecdotal story: andrew tridgell worked on the fujitsu sparc supercomputer a couple decades ago: it had a really weird DMA ring

Re: bcachefs status update (it's done cooking; let's get this sucker merged)

2019-06-19 Thread Jan Kara
On Thu 13-06-19 09:02:24, Dave Chinner wrote: > On Wed, Jun 12, 2019 at 12:21:44PM -0400, Kent Overstreet wrote: > > This would simplify things a lot and eliminate a really nasty corner case - > > page > > faults trigger readahead. Even if the buffer and the direct IO don't > > overlap, > >

Re: bcachefs status update (it's done cooking; let's get this sucker merged)

2019-06-13 Thread Dave Chinner
On Wed, Jun 12, 2019 at 12:21:44PM -0400, Kent Overstreet wrote: > On Tue, Jun 11, 2019 at 02:33:36PM +1000, Dave Chinner wrote: > > I just recently said this with reference to the range lock stuff I'm > > working on in the background: > > > > FWIW, it's to avoid problems with stupid

Re: bcachefs status update (it's done cooking; let's get this sucker merged)

2019-06-12 Thread Kent Overstreet
On Tue, Jun 11, 2019 at 02:33:36PM +1000, Dave Chinner wrote: > I just recently said this with reference to the range lock stuff I'm > working on in the background: > > FWIW, it's to avoid problems with stupid userspace stuff > that nobody really should be doing that I want range

Re: bcachefs status update (it's done cooking; let's get this sucker merged)

2019-06-11 Thread Linus Torvalds
On Mon, Jun 10, 2019 at 9:11 PM Dave Chinner wrote: > > The same rwsem issues were seen on the mmap_sem, the shrinker rwsem, > in a couple of device drivers, and so on. i.e. This isn't an XFS > issue I'm raising here - I'm raising a concern about the lack of > validation of core infrastructure

Re: bcachefs status update (it's done cooking; let's get this sucker merged)

2019-06-11 Thread Matthew Wilcox
On Mon, Jun 10, 2019 at 06:55:15PM -1000, Linus Torvalds wrote: > On Mon, Jun 10, 2019 at 3:17 PM Kent Overstreet > wrote: > > > Why does the regular page lock (at a finer granularity) not suffice? > > > > Because the lock needs to prevent pages from being _added_ to the page > > cache - > > to

Re: bcachefs status update (it's done cooking; let's get this sucker merged)

2019-06-11 Thread Dave Chinner
On Mon, Jun 10, 2019 at 06:39:00PM -1000, Linus Torvalds wrote: > On Mon, Jun 10, 2019 at 6:11 PM Dave Chinner wrote: > > > > Please, no, let's not make the rwsems even more fragile than they > > already are. I'm tired of the ongoing XFS customer escalations that > > end up being root caused to

Re: bcachefs status update (it's done cooking; let's get this sucker merged)

2019-06-10 Thread Linus Torvalds
On Mon, Jun 10, 2019 at 3:17 PM Kent Overstreet wrote: > > > > Why does the regular page lock (at a finer granularity) not suffice? > > Because the lock needs to prevent pages from being _added_ to the page cache - > to do it with a page granularity lock it'd have to be part of the radix tree,

Re: bcachefs status update (it's done cooking; let's get this sucker merged)

2019-06-10 Thread Linus Torvalds
On Mon, Jun 10, 2019 at 6:11 PM Dave Chinner wrote: > > Please, no, let's not make the rwsems even more fragile than they > already are. I'm tired of the ongoing XFS customer escalations that > end up being root caused to yet another rwsem memory barrier bug. > > > Have you talked to Waiman Long

Re: bcachefs status update (it's done cooking; let's get this sucker merged)

2019-06-10 Thread Dave Chinner
On Mon, Jun 10, 2019 at 09:17:37PM -0400, Kent Overstreet wrote: > On Mon, Jun 10, 2019 at 10:46:35AM -1000, Linus Torvalds wrote: > > On Mon, Jun 10, 2019 at 9:14 AM Kent Overstreet > > wrote: > > That lock is somewhat questionable in the first place, and no, we > > don't do those hacky

Re: bcachefs status update (it's done cooking; let's get this sucker merged)

2019-06-10 Thread Dave Chinner
On Mon, Jun 10, 2019 at 10:46:35AM -1000, Linus Torvalds wrote: > I also get the feeling that the "intent" part of the six-locks could > just be done as a slight extension of the rwsem, where an "intent" is > the same as a write-lock, but without waiting for existing readers, > and then the

Re: bcachefs status update (it's done cooking; let's get this sucker merged)

2019-06-10 Thread Kent Overstreet
On Mon, Jun 10, 2019 at 10:46:35AM -1000, Linus Torvalds wrote: > On Mon, Jun 10, 2019 at 9:14 AM Kent Overstreet > wrote: > > > > So. Here's my bcachefs-for-review branch - this has the minimal set of > > patches > > outside of fs/bcachefs/. My master branch has some performance > >

Re: bcachefs status update (it's done cooking; let's get this sucker merged)

2019-06-10 Thread Linus Torvalds
On Mon, Jun 10, 2019 at 9:14 AM Kent Overstreet wrote: > > So. Here's my bcachefs-for-review branch - this has the minimal set of patches > outside of fs/bcachefs/. My master branch has some performance optimizations > for > the core buffered IO paths, but those are fairly tricky and invasive so

bcachefs status update (it's done cooking; let's get this sucker merged)

2019-06-10 Thread Kent Overstreet
Last status update: https://lkml.org/lkml/2018/12/2/46 Current status - I'm pretty much running out of things to polish and excuses to keep tinkering. The core featureset is _done_ and the list of known outstanding bugs is getting to be short and unexciting. The next big things on my todo list