public inbox for linux-scsi@vger.kernel.org
 help / color / mirror / Atom feed
From: Brian King <brking@us.ibm.com>
To: dougg@torque.net
Cc: linux-scsi@vger.kernel.org, david.falkinder@hp.com
Subject: Re: [PATCH] sg driver for large page_size, lk 2.6.18
Date: Fri, 22 Sep 2006 16:23:00 -0500	[thread overview]
Message-ID: <45145434.4080007@us.ibm.com> (raw)
In-Reply-To: <4511BEC1.8030809@torque.net>

Douglas Gilbert wrote:
> This sg driver patch addresses the problem with larger
> page sizes reported by Brian King in this post:
> http://marc.theaimsgroup.com/?l=linux-scsi&m=115867718623631&w=2

This fixes the oops I was seeing on PPC64 with 64k pages
enabled.

Brian


> Some other related matters are also addressed. Some of these
> prevent oopses when the SG_SCATTER_SZ or scatter_elem_sz are
> set to inappropriate values.
> 
> The scatter_elem_sz has been tested up to 4 MB which should
> make the largest data transfer with one SCSI command, 32 MB
> less one block, achievable with a relatively small number
> of elements in the scatter gather list.
> 
> For consideration in lk 2.6.19 . The patch is against lk 2.6.18 .
> 
>   ChangeLog:
>     - add scatter_elem_sz boot time parameter and sysfs module
>       parameter that is initialized to SG_SCATTER_SZ
>     - the driver will then adjust scatter_elem_sz to be the
>       max(given(scatter_elem_sz), PAGE_SIZE)
>       It will also round it up, if necessary, to be a power
>       of two
>     - clean up sg.h header, correct bad urls and some statements
>       that are no longer valid
>     - make the def_reserved_size sysfs module attribute writable
> 
> Signed-off-by: Douglas Gilbert <dougg@torque.net>
> 
> Doug Gilbert
> 


-- 
Brian King
eServer Storage I/O
IBM Linux Technology Center

      reply	other threads:[~2006-09-22 21:23 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-09-20 22:20 [PATCH] sg driver for large page_size, lk 2.6.18 Douglas Gilbert
2006-09-22 21:23 ` Brian King [this message]

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=45145434.4080007@us.ibm.com \
    --to=brking@us.ibm.com \
    --cc=david.falkinder@hp.com \
    --cc=dougg@torque.net \
    --cc=linux-scsi@vger.kernel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox