[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <556445368AFA1C438794ABDA8901891C0999203A@USA0300MS03.na.xerox.net>
Date: Fri, 26 Sep 2008 11:51:34 -0400
From: "Leisner, Martin" <Martin.Leisner@...ox.com>
To: "Jens Axboe" <jens.axboe@...cle.com>,
"Alan Cox" <alan@...rguk.ukuu.org.uk>
Cc: "marty" <martyleisner@...oo.com>, <linux-kernel@...r.kernel.org>
Subject: RE: disk IO directly from PCI memory to block device sectors
> -----Original Message-----
> From: Jens Axboe [mailto:jens.axboe@...cle.com]
> Sent: Friday, September 26, 2008 5:12 AM
> To: Alan Cox
> Cc: marty; linux-kernel@...r.kernel.org; Leisner, Martin
> Subject: Re: disk IO directly from PCI memory to block device
sectors
>
> 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.
>
> --
> Jens Axboe
Also:
a) to deal with interrupts from the hardware
b) using legacy code/design/architecture
The splice approaches look very interesting...thanks...
marty
--
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/
Powered by blists - more mailing lists