linux-kernel - Re: disk IO directly from PCI memory to block device sectors

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]

Date:	Fri, 26 Sep 2008 11:06:10 +0100
From:	Alan Cox <alan@...rguk.ukuu.org.uk>
To:	Jens Axboe <jens.axboe@...cle.com>
Cc:	marty <martyleisner@...oo.com>, linux-kernel@...r.kernel.org,
	martin.leisner@...ox.com
Subject: Re: disk IO directly from PCI memory to block device sectors

On Fri, 26 Sep 2008 11:11:35 +0200
Jens Axboe <jens.axboe@...cle.com> wrote:

> On Fri, Sep 26 2008, Alan Cox wrote:
> > > What I'm looking is for a more generic/driver independent way of sticking
> > > contents of PCI ram onto a disk.
> > 
> > Ermm seriously why not have a userspace task with the PCI RAM mmapped
> > and just use write() like normal sane people do ?
> 
> To avoid the fault and copy, I would assume.

It's a write to a raw partition so with O_DIRECT you won't have to copy
and MAP_POPULATE will premap the object if even the first write wants to
occur without faulting overhead.

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/