õ?îLK¶H7$~Á}4Ú¥(ÀסÅc
Hîeg»Í-·`îG%æÐÒf(L4xDû"ò#Tý"ª«Ë`þ¯°#bÐd7àjøë¾øÀ(D.Åé<
õ
X«©Ò¾%ëÎc¥ÃH¶ÈúÀóþü:áÎj7¿Áïͬ³âH#|ëQjßø ±¡T6QT¢UÀR1x´R¸(>ª8àQ0XB
`Úõ²d×U/ÅÂàZõuQáw¨¢ôI6nåPc7À¨:oPbHlø?¹5ëÌsDçlÆTCE%ì<ò_Pbèv|ñ5¿äwQKvV1hu\8ñ×ä.â¦Mï²·/q3í
On Thu, Apr 19, 2018 at 3:44 AM, Jan Kara wrote:
> On Fri 13-04-18 15:03:51, Dan Williams wrote:
>> On Mon, Apr 9, 2018 at 9:51 AM, Dan Williams
>> wrote:
>> > On Mon, Apr 9, 2018 at 9:49 AM, Jan Kara wrote:
>> >> On Sat 07-04-18 12:38:24,
I was comparing different caching techniques using MTRR entries and I
found something strange. Note the output is from a basic utility that
uses mmap.
NV Memory:
Write-back
Writes took 2075.993408 Megabytes per second
Reads took 2130.842529 Megabytes per second No Errors Found
Write-Through
On Thu, Apr 19, 2018 at 1:39 PM, Dave Jiang wrote:
> MAP_SYNC is a nop for device-dax. Allow MAP_SYNC to succeed on device-dax
> to eliminate special casing between device-dax and fs-dax as to when the
> flag can be specified. Device-dax users already implicitly assume that
MAP_SYNC is a nop for device-dax. Allow MAP_SYNC to succeed on device-dax
to eliminate special casing between device-dax and fs-dax as to when the
flag can be specified. Device-dax users already implicitly assume that they do
not need to call fsync(), and this enables them to explicitly check for
I'll change the "allowing" to "allow" in the subject so we don't have
a gerund phrase.
On Thu, Apr 19, 2018 at 11:22 AM, Dave Jiang wrote:
> MAP_SYNC is basically a nop for device-dax. However allowing the MAP_SYNC
Not "bascially", it *is* a nop for device-dax. I'll change
MAP_SYNC is basically a nop for device-dax. However allowing the MAP_SYNC
flag to succeed on device-dax would make it consistent with fs-dax and
reduces confusion for the application writer. This allows the application to
assume that it does not need to call fsync() after writes to device-dax
On Thu, 19 Apr 2018 17:11:17 +0200,
Takashi Iwai wrote:
>
> Hi,
>
> this is a revised patchset to add the support for asciidoctor to
> generate documents. The reason for adding this feature is that the
> future of asciidoc isn't clear as it's written in python2, which is
> now hated by all
This patch adds the support for asciidoctor to be used for generating
documents instead of asciidoc. It's enabled via --enable-asciidoctor
configure option while asciidoc is used still as default.
In addition to the configure option, a few other changes were needed:
* some asciidoc.conf python
The length of the title and section marker has to be aligned with the
previous line. This was caught when running asciidoctor, which is
more strict than asciidoc.
Also since asciidoctor doesn't like the verse block in some cases,
replace the code examples with simpler markers.
Signed-off-by:
Hi,
this is a revised patchset to add the support for asciidoctor to
generate documents. The reason for adding this feature is that the
future of asciidoc isn't clear as it's written in python2, which is
now hated by all people out of sudden :)
The asciidoctor support is enabled via configure
Two new files were added for asciidoctor support.
Signed-off-by: Takashi Iwai
---
.gitignore | 2 ++
1 file changed, 2 insertions(+)
diff --git a/.gitignore b/.gitignore
index 20a04dedd862..c7d11d91398c 100644
--- a/.gitignore
+++ b/.gitignore
@@ -15,6 +15,8 @@ Makefile.in
*.1
On Fri 13-04-18 15:03:51, Dan Williams wrote:
> On Mon, Apr 9, 2018 at 9:51 AM, Dan Williams wrote:
> > On Mon, Apr 9, 2018 at 9:49 AM, Jan Kara wrote:
> >> On Sat 07-04-18 12:38:24, Dan Williams wrote:
> > [..]
> >>> I wonder if this can be trivially
13 matches
Mail list logo