linux-kernel - Re: [PATCH 0/4] Page based O

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-Id: <1250720604.5589.50.camel@cail>
Date:	Wed, 19 Aug 2009 18:23:24 -0400
From:	"Alan D. Brunelle" <Alan.Brunelle@...com>
To:	Jens Axboe <jens.axboe@...cle.com>
Cc:	linux-kernel@...r.kernel.org, zach.brown@...cle.com,
	hch@...radead.org
Subject: Re: [PATCH 0/4] Page based O_DIRECT v2

On Thu, 2009-08-20 at 00:06 +0200, Jens Axboe wrote:

> 
> Thanks a lot for the test run, Alan. I wonder why writes are down while
> reads are up. One possibility could be a WRITE vs WRITE_ODIRECT
> difference, though I think they should be the same. The patches I posted
> have not been benchmarked at all, it's still very much a work in
> progress. I just wanted to show the general direction that I thought
> would be interesting. So I have done absolutely zero performance
> testing, it's only been tested for whether it still worked or not (to
> some degree :-)...
> 
> I'll poke a bit at it here, too. I want to finish the unplug/wait
> problem first. Is your test case using read/write or readv/writev?
> 

Hi Jens - I just had some extra cycles, so figured what the heck... :-)

Actually, this is using asynchronous direct I/Os (libaio/Linux native
AIO). If I get a chance tomorrow, I'll play with read/write (and/or
readv/writev). 

Alan

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