All of lore.kernel.org
 help / color / mirror / Atom feed
From: Mike Christie <michaelc@cs.wisc.edu>
To: James Bottomley <James.Bottomley@SteelEye.com>
Cc: dougg@torque.net, Linus Torvalds <torvalds@osdl.org>,
	Matthias Andree <matthias.andree@gmx.de>,
	Mark Rustad <mrustad@mac.com>,
	linux-scsi@vger.kernel.org,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: sg regression in 2.6.16-rc5
Date: Wed, 01 Mar 2006 16:56:58 -0600	[thread overview]
Message-ID: <440626BA.4070000@cs.wisc.edu> (raw)
In-Reply-To: <1141252235.3276.63.camel@mulgrave.il.steeleye.com>

James Bottomley wrote:
> On Wed, 2006-03-01 at 14:42 -0600, Mike Christie wrote:
> 
>>The current sg driver should use alloc_pages() with an order that should
>>get 32 KB. If the order being passed to alloc_pages() in sg.c is only
>>getting one page by default that is bug.
> 
> 
>>The generic routines now being used can turn that 32KB segment into
>>multiple 4KB ones if the LLD does not support clustering.
> 
> 
> To be honest, the original behaviour was a bug.  A device that doesn't
> enable clustering is telling us it can't take anything other than
> PAGE_SIZE chunks ... trying to give it more is likely to end in tears.

Yeah, we hit this with iscsi_tcp. iscsi_tcp does not suport clustering, 
not due to a HW limit, but becuase that is just how it was implemented. 
When we get clustered segments we end up with data corruption or an oops 
depending on the operation. I think the workaround was to set the 
default segment for sg and st to a page or just use the block layer sg_io.

> 
> However ... I'm not sure we actually have any devices that anyone can
> identify which truly can't enable clustering (a lot which have it
> disabled, I suspect, are that way historically because their writers
> didn't trust the clustering algorithm).
> 

ok, I can implement clustering for iscsi_tcp. For now it does not much 
matter since we never supported large sg or st commands.

  reply	other threads:[~2006-03-01 22:57 UTC|newest]

Thread overview: 34+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-02-28 17:54 sg regression in 2.6.16-rc5 Mark Rustad
2006-02-28 19:53 ` Douglas Gilbert
2006-02-28 20:38   ` Kai Makisara
2006-03-01  2:04     ` Douglas Gilbert
2006-03-01  2:08     ` Mark Rustad
2006-03-01  8:38   ` Matthias Andree
2006-03-01 18:28     ` Linus Torvalds
2006-03-01 18:32       ` Mark Lord
2006-03-01 18:42         ` Linus Torvalds
2006-03-01 18:50           ` Matthew Wilcox
2006-03-03 18:27           ` Steve Byan
2006-03-03 18:55             ` Linus Torvalds
2006-03-03 19:13               ` Steve Byan
2006-03-03 19:42               ` Jeff Garzik
2006-03-03 20:09                 ` Linus Torvalds
2006-03-03 20:30                   ` Jeff Garzik
2006-03-01 19:33       ` Douglas Gilbert
2006-03-01 20:42         ` Mike Christie
2006-03-01 22:30           ` James Bottomley
2006-03-01 22:56             ` Mike Christie [this message]
2006-03-01 21:06         ` Kai Makisara
2006-03-02 19:50           ` Douglas Gilbert
2006-03-02 21:25             ` Linus Torvalds
2006-03-02 23:08               ` Matthias Andree
2006-03-02 23:20                 ` Linus Torvalds
2006-03-03  0:02                   ` Linus Torvalds
2006-03-03  0:12                     ` Linus Torvalds
2006-03-03 16:43                   ` Douglas Gilbert
2006-03-03 17:17                     ` Linus Torvalds
2006-03-02 23:06             ` Matthias Andree
  -- strict thread matches above, loose matches on Subject: below --
2006-03-02 23:04 Falkinder, David Malcolm
2006-03-02 23:04 ` Falkinder, David Malcolm
2006-03-03 20:24 Falkinder, David Malcolm
2006-03-03 21:54 ` Linus Torvalds

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=440626BA.4070000@cs.wisc.edu \
    --to=michaelc@cs.wisc.edu \
    --cc=James.Bottomley@SteelEye.com \
    --cc=dougg@torque.net \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-scsi@vger.kernel.org \
    --cc=matthias.andree@gmx.de \
    --cc=mrustad@mac.com \
    --cc=torvalds@osdl.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.