Re: Direct I/O

2019-09-18 Thread Michael McCandless
> We should better make a proposal for f/madvise. The jdk people are open >>>> for that, and I am jdk committer now, so I can make a prototype. >>>> >>>> Uwe >>>> >>>> Am

Re: Direct I/O

2019-09-18 Thread Uwe Schindler
t that restricted to aligned block-only access though? I can >>>> imagine this would complicate the implementation if somebody wanted >to >>>> use it directly. >>>> >>>> Dawid >>>> >>>> On Tue, Sep 17, 2019 at 5:37 PM Michael McCa

Re: Direct I/O

2019-09-18 Thread Dawid Weiss
itter now, so I can make a prototype. >> >> Uwe >> >> Am September 17, 2019 4:48:26 PM UTC schrieb Dawid Weiss >> : >>> >>> Isn't that restricted to aligned block-only access though? I can >>> imagine this would complicate the implementation if s

Re: Direct I/O

2019-09-18 Thread Michael McCandless
ber 17, 2019 4:48:26 PM UTC schrieb Dawid Weiss < >> dawid.we...@gmail.com>: >>> >>> Isn't that restricted to aligned block-only access though? I can >>> imagine this would complicate the implementation if somebody wanted to >>> use it directly. >

Re: Direct I/O

2019-09-18 Thread Michael McCandless
ep 17, 2019 at 5:37 PM Michael McCandless >> wrote: >> >>> >>> Whoa! That would be awesome -- no more JNI to use Direct I/O? >>> Looks like you use it like this: >>> >>> FileChannel fc = FileChannel.open(p, StandardOpenOption.W

Re: Direct I/O

2019-09-18 Thread Michael McCandless
ted to >> use it directly. >> >> Dawid >> >> On Tue, Sep 17, 2019 at 5:37 PM Michael McCandless >> wrote: >> >>> >>> Whoa! That would be awesome -- no more JNI to use Direct I/O? >>> Looks like you use it like

Re: Direct I/O

2019-09-17 Thread Uwe Schindler
s > wrote: >> >> Whoa! That would be awesome -- no more JNI to use Direct I/O? >> Looks like you use it like this: >> >> FileChannel fc = FileChannel.open(p, StandardOpenOption.WRITE, >> ExtendedOpenOption.DIRECT >> >>

Re: Direct I/O

2019-09-17 Thread Dawid Weiss
Isn't that restricted to aligned block-only access though? I can imagine this would complicate the implementation if somebody wanted to use it directly. Dawid On Tue, Sep 17, 2019 at 5:37 PM Michael McCandless wrote: > > Whoa! That would be awesome -- no more JNI to use Direct I/O? &

Re: Direct I/O

2019-09-17 Thread Michael McCandless
Whoa! That would be awesome -- no more JNI to use Direct I/O? Looks like you use it like this: FileChannel fc = FileChannel.open(p, StandardOpenOption.WRITE, ExtendedOpenOption.DIRECT But it looks like you need to enable the jdk.unsupported module, added

Direct I/O

2019-09-16 Thread Michael Sokolov
https://bugs.openjdk.java.net/browse/JDK-8189192 makes it appear that Direct I/O is (or may be?) available now in JDK's since JDK10. Should we try using that API in NativeUnixDirectory in order to avoid JNI calls