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] [day] [month] [year] [list]
Date:	Fri, 15 Aug 2008 08:19:30 -0400
From:	Andrew Gallatin <gallatin@...i.com>
To:	David Miller <davem@...emloft.net>
CC:	rick.jones2@...com, rdreier@...co.com, jgarzik@...ox.com,
	swise@...ngridcomputing.com, divy@...lsio.com, kxie@...lsio.com,
	netdev@...r.kernel.org, open-iscsi@...glegroups.com,
	michaelc@...wisc.edu, daisyc@...ibm.com, wenxiong@...ibm.com,
	bhua@...ibm.com, dm@...lsio.com, lee@...per.es
Subject: Re: [RFC][PATCH 1/1] cxgb3i: cxgb3 iSCSI initiator

David Miller wrote:
 > From: Andrew Gallatin <gallatin@...i.com>
 > Date: Thu, 14 Aug 2008 16:45:57 -0400
 >
 >> Speaking of stateless data placement.  Assume you have a page or set
 >> of pages allocated by a network driver which contain exactly the data
 >> a block driver is interested in to fulfill a read request (eg, the NIC
 >> understands the protocol just well enough to split headers).  Is it
 >> possible in the block driver to simply replace the pages that are
 >> attached to the buf with pages allocated by the network driver?
 >>
 >> It was my impression that the pages associated with a buf are in
 >> fairly magical states and that you cannot replace them.
 >
 > This, if true, would be quite easy to rectify.

That's great news.

The reason I think this is because a few months ago, I tried to make
the AOE block driver zero-copy on read.  I modified the myri10ge
ethernet driver and firmware to split AOE headers, so that the AOE
read data started nicely aligned in a page allocated by myri10ge.
(this obviously only works for for jumbo MTUs..).  This part was
trivial, but I got bogged down trying to figure out how to replace the
buf associated pages in the AOE driver, as they seemed to be in
various states of entanglement with the LRU and page caches.

I'm more of a network driver guy, and my lack of understanding of the
block layer and page cache probably made me give up too quickly.  I'll
dust off this work and ask for help.

Thanks,

Drew
--
To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ