Re: [RFC PATCH] fpathconf() for fsync() behavior

[Jeff Garzik]

Theodore Tso wrote:
> So we can create a more finer-grained controlled system call ---
> although I would suggest that we just add some extra flags to
> sync_file_range() --- but it's doubtful that many application
> programmers will use it.

sync_file_range() seems the obvious avenue for new fsync flags.

I even explored what it would take to add a "flush storage dev writeback 
cache, for this file" flag to sync_file_range(), rather unfortunately 
non-trivial given the current implementation's close ties to MM.

But yeah...  how many people will use these fancy new flags and features?

	Jeff



--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/