All of lore.kernel.org
 help / color / mirror / Atom feed
From: Michael Reed <mdr@sgi.com>
To: Guennadi Liakhovetski <g.liakhovetski@gmx.de>
Cc: linux-scsi@vger.kernel.org
Subject: Re: SCSI tape block size
Date: Thu, 28 Sep 2006 09:34:44 -0500	[thread overview]
Message-ID: <451BDD84.2060704@sgi.com> (raw)
In-Reply-To: <Pine.LNX.4.60.0609272246320.7350@poirot.grange>



Guennadi Liakhovetski wrote:
> Hi all
> 
> I've got a problem report and a patch from John Adams, he says tmscsim 
> driver under 2.6.17 and on doesn't allow him to read tapes with blocksize 
> of 1MB. He fixes this with the below patch.
> 
> On Sun, 24 Sep 2006, John Adams wrote:
> 
>> --- drivers/scsi/tmscsim.c.bak	2006-09-24 12:55:08.000000000 -0400
>> +++ drivers/scsi/tmscsim.c	2006-09-24 12:55:56.000000000 -0400
>> @@ -2300,7 +2300,8 @@
>>  	.this_id		= 7,
>>  	.sg_tablesize		= SG_ALL,
>>  	.cmd_per_lun		= 1,
>> -	.use_clustering		= DISABLE_CLUSTERING,
>> +	.use_clustering		= ENABLE_CLUSTERING,
>> +	.max_sectors            = 2048,
>>  };
>>  
>>  /***********************************************************************
> 
> It looks like
> 
> 1) use_clustering doesn't directly affect maximum block size, so, he 
> doesn't really need it, although, it might make sense for tmscsim to 
> improve performance.
> 
> 2) max_sectors is indeed what he needs, but it looks strange that now it 
> has to be set by the low-level driver... For block devices you can set it 
> at run time with /sys/block/sda/queue/max_sectors_kb, right? But what 
> about tapes?

Thank you for posting this.  I was wondering why with 2.6.16 the maximum
tape block I could access via by BusLogic adapter dropped to 64k.  Now
I know what to change.

Does anyone know what the appropriate max sectors limit is for BusLogic?

Thanks,
 Mike

> 
> Sorry, didn't find too much documentation about it.
> 
> Thanks
> Guennadi
> ---
> Guennadi Liakhovetski
> -
> To unsubscribe from this list: send the line "unsubscribe linux-scsi" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html
> 
> 

  reply	other threads:[~2006-09-28 14:35 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <200609241605.32327.johna@onevista.com>
2006-09-27 21:32 ` SCSI tape block size Guennadi Liakhovetski
2006-09-28 14:34   ` Michael Reed [this message]
2006-09-28 19:47   ` Kai Makisara
2006-09-28 20:41     ` use_clustering again (was Re: SCSI tape block size) Guennadi Liakhovetski
2006-09-28 19:50       ` Mike Christie
2006-09-28 21:36         ` use_clustering again Martin K. Petersen
2006-09-30 20:52     ` SCSI tape block size Guennadi Liakhovetski
2006-10-01 10:42       ` Kai Makisara
2006-10-01 17:05         ` Guennadi Liakhovetski

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=451BDD84.2060704@sgi.com \
    --to=mdr@sgi.com \
    --cc=g.liakhovetski@gmx.de \
    --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 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.