On Thu, Dec 13 2007 at 20:43 +0200, [EMAIL PROTECTED] wrote:
From: Mike Christie [EMAIL PROTECTED]
The previous patches converted iscsi_tcp to support sg chaining.
This patch sets the proper flags and sets sg_table size to
4096. This allows fs io to be capped at max_sectors, but passthrough
On Sat, Dec 15 2007 at 2:27 +0200, James Bottomley [EMAIL PROTECTED] wrote:
On Tue, 2007-09-18 at 17:04 +0200, Boaz Harrosh wrote:
On Wed, Sep 12 2007 at 10:42 +0300, Russell King [EMAIL PROTECTED] wrote:
On Wed, Sep 12, 2007 at 02:55:19AM +0300, Boaz Harrosh wrote:
- if
This patch speeds up sbp2 a little bit --- but more importantly, it
brings the behavior of sbp2 and fw-sbp2 closer to each other. Like
fw-sbp2, sbp2 now does not limit the size of single transfers to 255
sectors anymore, unless told so by a blacklist flag or by module load
parameters.
Only very
Just using cp to read the file is enough to cause problems but I included
a very basic program below that produces the BUG_ON checks. Is this a known
issue or am I using the interface incorrectly?
I'd say you're using it correctly but you've found a hitherto unknown bug.
On i386 highmem
On (14/12/07 13:07), Mark Lord didst pronounce:
SNIP
That (also) works for me here, regularly generating 64KB I/O segments with
SLAB.
Brilliant. Thanks a lot Mark.
--
Mel Gorman
Part-time Phd Student Linux Technology Center
University of Limerick
Hi,
This looks to be a regression between 2.6.23 and 2.6.24-rc5, I'll try
to bi-sect this and report more on it. Basically, when I bootup, I
get a ton of errors in the dmesg log along the lines of:
[ 215.007701] sym1: SCSI parity error detected: SCR1=1 DBC=1128 SBCL=ae
[ 215.008145]
On Sun, 16 Dec 2007 20:05:51 -0500
John Stoffel [EMAIL PROTECTED] wrote:
[ 215.007701] sym1: SCSI parity error detected: SCR1=1 DBC=1128 SBCL=ae
[ 215.008145] sym1: SCSI parity error detected: SCR1=1 DBC=1128 SBCL=ae
[ 215.008678] sym1: SCSI parity error detected: SCR1=1
7 matches
Mail list logo