On Wed, 16 Jan 2008 14:35:50 +0200
Benny Halevy <[EMAIL PROTECTED]> wrote:
> On Jan. 15, 2008, 17:20 +0200, James Bottomley <[EMAIL PROTECTED]> wrote:
> > On Tue, 2008-01-15 at 18:23 +0900, FUJITA Tomonori wrote:
> >> This is the second version of
> >>
> >> http://marc.info/?l=linux-scsi&m=1199336
Hello,
I have performed a test to compare the performance of SCST and STGT.
Apparently the SCST target implementation performed far better than
the STGT target implementation. This makes me wonder whether this is
due to the design of SCST or whether STGT's performance can be
improved to the level
FUJITA Tomonori wrote:
On Thu, 17 Jan 2008 10:27:08 +0100
"Bart Van Assche" <[EMAIL PROTECTED]> wrote:
Hello,
I have performed a test to compare the performance of SCST and STGT.
Apparently the SCST target implementation performed far better than
the STGT target implementation. This makes me
On Thu, 17 Jan 2008 10:27:08 +0100
"Bart Van Assche" <[EMAIL PROTECTED]> wrote:
> Hello,
>
> I have performed a test to compare the performance of SCST and STGT.
> Apparently the SCST target implementation performed far better than
> the STGT target implementation. This makes me wonder whether th
On Thu, 17 Jan 2008 12:48:28 +0300
Vladislav Bolkhovitin <[EMAIL PROTECTED]> wrote:
> FUJITA Tomonori wrote:
> > On Thu, 17 Jan 2008 10:27:08 +0100
> > "Bart Van Assche" <[EMAIL PROTECTED]> wrote:
> >
> >
> >>Hello,
> >>
> >>I have performed a test to compare the performance of SCST and STGT.
>
FUJITA Tomonori wrote:
On Thu, 17 Jan 2008 12:48:28 +0300
Vladislav Bolkhovitin <[EMAIL PROTECTED]> wrote:
FUJITA Tomonori wrote:
On Thu, 17 Jan 2008 10:27:08 +0100
"Bart Van Assche" <[EMAIL PROTECTED]> wrote:
Hello,
I have performed a test to compare the performance of SCST and STGT.
A
On Mon, 2008-01-14 at 19:31 +0100, Stefan Richter wrote:
> Bill Adair wrote:
> > Is there any way under Linux of forcing use of the sd driver for a
> > device on the bus instead of sg?
>
> The INQUIRY data which the SCSI core gets from the device have to
> indicate that the device implements SBC
LLDs don't need to zero out scsi_cmnd::sense_buffer in queuecommand
since scsi-ml does. This is a preparation of the future changes to
allocate the sense_buffer only when necessary.
Signed-off-by: FUJITA Tomonori <[EMAIL PROTECTED]>
---
drivers/scsi/atp870u.c |1 -
1 files changed, 0 insertio
On Thu, Jan 17, 2008 at 01:34:46PM +0300, Vladislav Bolkhovitin wrote:
>Hmm, I can't find which IB hardware did he use and it's declared Gbps
>speed. He declared only "Mellanox 4X SDR, switch". What does it mean?
SDR is 10Gbit carrier, at most about ~900MB/s data rate.
DDR is 20Gbit carrier, at
Robin Humble wrote:
On Thu, Jan 17, 2008 at 01:34:46PM +0300, Vladislav Bolkhovitin wrote:
Hmm, I can't find which IB hardware did he use and it's declared Gbps
speed. He declared only "Mellanox 4X SDR, switch". What does it mean?
SDR is 10Gbit carrier, at most about ~900MB/s data rate.
DDR
FUJITA Tomonori wrote:
> On Thu, 17 Jan 2008 12:48:28 +0300
> Vladislav Bolkhovitin <[EMAIL PROTECTED]> wrote:
>
>
>> FUJITA Tomonori wrote:
>>
>>> On Thu, 17 Jan 2008 10:27:08 +0100
>>> "Bart Van Assche" <[EMAIL PROTECTED]> wrote:
>>>
>>>
>>>
Hello,
I have performed a
On Jan 17, 2008 1:29 PM, Robin Humble <[EMAIL PROTECTED]> wrote:
> was iscsiadm was pointed at the IP of the IPoIB interface on the target? I
> think tgtd requires that.
>
> how about setting the transport to be iser with eg.
> iscsiadm --mode node --targetname --portal :3260 --op
> update -n
>> We didn't run any real performance test with tgt, so I don't have
>> numbers yet. I know that Pete got ~900 MB/sec by hacking sgp_dd, so all
>> data was read/written to the same block (so it was all done in the
>> cache). Pete - am I right?
>>
>> As already mentioned, he got that with IB SDR ca
Hi Andrew,
The kernel build fails with following error
drivers/scsi/aha152x.o: In function `aha152x_host_reset_host':
/home/kamalesh/scrap/linux-2.6.24-rc8/drivers/scsi/aha152x.c:1324: multiple
definition of `aha152x_host_reset_host'
drivers/scsi/pcmcia/built-in.o:/home/kamalesh/scrap/linux-2.6.
On Thu, 2008-01-17 at 18:13 +0900, FUJITA Tomonori wrote:
> On Wed, 16 Jan 2008 14:35:50 +0200
> Benny Halevy <[EMAIL PROTECTED]> wrote:
>
> > On Jan. 15, 2008, 17:20 +0200, James Bottomley <[EMAIL PROTECTED]> wrote:
> > > On Tue, 2008-01-15 at 18:23 +0900, FUJITA Tomonori wrote:
> > >> This is t
On Thu, 2008-01-17 at 14:37 +, David wrote:
> I have here a server with an LSI SCSI card. On one channel is a tape
> changer, on the other an external RAID5 box with a number of disks in.
> All worked fine until a recent upgrade and now the disk array is not
> recognised.
>
> The dis
Erez Zilber wrote:
FUJITA Tomonori wrote:
On Thu, 17 Jan 2008 12:48:28 +0300
Vladislav Bolkhovitin <[EMAIL PROTECTED]> wrote:
FUJITA Tomonori wrote:
On Thu, 17 Jan 2008 10:27:08 +0100
"Bart Van Assche" <[EMAIL PROTECTED]> wrote:
Hello,
I have performed a test to compare th
I have here a server with an LSI SCSI card. On one channel is a tape
changer, on the other an external RAID5 box with a number of disks in.
All worked fine until a recent upgrade and now the disk array is not
recognised.
The disk array is still recognised on machine startup in the SCSI ca
On Thu, 2008-01-17 at 10:53 +, Bill Adair wrote:
> On Mon, 2008-01-14 at 19:31 +0100, Stefan Richter wrote:
> > Bill Adair wrote:
> > > Is there any way under Linux of forcing use of the sd driver for a
> > > device on the bus instead of sg?
> >
> > The INQUIRY data which the SCSI core gets f
Change the definition of SG_ALL from 255, which was the biggest possible
scatter list array in 32 bit ARCHs (minus one who knows why), to be ~0.
Which means that LLD has no size limit on number of scatter-list array
and the actual size will be determined by upper layers.
Also SG_NONE is
These drivers used the SG_ALL constant, But actually
meant some other define.
Signed-off-by: Boaz Harrosh <[EMAIL PROTECTED]>
---
drivers/scsi/a100u2w.c |3 +--
drivers/scsi/advansys.c |8 +++-
drivers/scsi/initio.c |2 +-
3 files changed, 5 insertions(+), 8 deletions(-)
arm-scsi core is not sg-chain ready, so maximum scatterlist supported
is SCSI_MAX_SG_SEGMENTS. Define it so, in core, and let all drivers
use it for the sg_tablesize in host templates.
Signed-off-by: Boaz Harrosh <[EMAIL PROTECTED]>
---
drivers/scsi/arm/acornscsi.c |2 +-
drivers/scsi/
wd33c93 core is not sg-chain ready, so maximum scatterlist supported
is SCSI_MAX_SG_SEGMENTS. Define it so, in core, and let all drivers
use it for the sg_tablesize in host templates.
Signed-off-by: Boaz Harrosh <[EMAIL PROTECTED]>
---
drivers/scsi/a2091.c |2 +-
drivers/scsi/a3000.c
NCR5380 core is not sg-chain ready, so maximum scatterlist supported
is SCSI_MAX_SG_SEGMENTS. Define it so, in core, and let all drivers
use it for the sg_tablesize in host templates.
Signed-off-by: Boaz Harrosh <[EMAIL PROTECTED]>
---
drivers/scsi/NCR5380.h |3 +++
drivers/scsi/
below list of drivers have used SG_ALL as a size to
preallocate maximum possible command's sg-count.
This is no longer possible since the maximum is not
set at compile time but as a run time configuration.
A better schema can be advised with a more dynamic allocation.
Perhaps from a k
SG_ALL wants to be ~0 meaning "any future size".
Below group of drivers preallocate a scatter list
buffer of max_size, so set that size to be 255 (Like before).
A better schema can be advised with a more dynamic allocation.
Perhaps from a kmem_cache.
List of drivers/files:
dr
I have scanned through the scsi tree and checked all places that used
SG_ALL. Those drivers that where not ready for SG_ALL to mean "any size"
where changed to what ever is appropriate for this driver.
Mainly 3 groups.
Those that meant SG_ALL == 255:
[PATCH 1/8] firewire: ieee1394: Move away f
All below drivers are not sg-chain ready do to incomplete software.
Once fixed they can move back to SG_ALL. For now they are stuck on
SCSI_MAX_SG_SEGMENTS.
Affected drivers/files:
drivers/scsi/aha152x.c
drivers/scsi/esp_scsi.[ch]
drivers/scsi/imm.c
drivers
On Thu, 17 Jan 2008, Boaz Harrosh wrote:
> below list of drivers have used SG_ALL as a size to
> preallocate maximum possible command's sg-count.
> This is no longer possible since the maximum is not
> set at compile time but as a run time configuration.
>
> A better schema can be advis
Feature enhancement, adding a 'flags' entry that will reside in the host
controller's tree, with a newline separated list of arbitrary ascii named
features that indicate whether the combination of driver and controller has
support for said feature. Breaking from the one-line output typical of sy
On Thu, 17 Jan 2008, James Bottomley wrote:
> On Thu, 2008-01-17 at 09:33 -0800, Andrew Vasquez wrote:
> > On Thu, 17 Jan 2008, Andrew Vasquez wrote:
> >
> > > This patchset updates the qla2xxx driver to 8.02.00-k7.
> > ...
> >
> >
> > BTW: Small typo in the subject, it's obvious these patches
Boaz Harrosh wrote:
> SG_ALL wants to be ~0 meaning "any future size".
> Below group of drivers preallocate a scatter list
> buffer of max_size, so set that size to be 255 (Like before).
>
> A better schema can be advised with a more dynamic allocation.
> Perhaps from a kmem_cache.
>
>
Boaz Harrosh wrote:
> Those that meant SG_ALL == 255:
>
> [PATCH 1/8] firewire: ieee1394: Move away from SG_ALL
They simply mean SG_ALL == something, as long as it isn't unreasonably
small or large.
--
Stefan Richter
-=-==--- ---= =---=
http://arcgraph.de/sr/
-
To unsubscribe from this lis
On Thu, 2008-01-17 at 09:33 -0800, Andrew Vasquez wrote:
> On Thu, 17 Jan 2008, Andrew Vasquez wrote:
>
> > This patchset updates the qla2xxx driver to 8.02.00-k7.
> ...
>
>
> BTW: Small typo in the subject, it's obvious these patches aren't for
> 2.6.24, instead, meant for the next merge wind
On Thu, Jan 17 2008 at 19:47 +0200, Andrew Vasquez <[EMAIL PROTECTED]> wrote:
> On Thu, 17 Jan 2008, Boaz Harrosh wrote:
>
>> below list of drivers have used SG_ALL as a size to
>> preallocate maximum possible command's sg-count.
>> This is no longer possible since the maximum is not
>> se
In preparation for FCE (Fibre Channel Event) tracing support.
Signed-off-by: Andrew Vasquez <[EMAIL PROTECTED]>
---
drivers/scsi/qla2xxx/qla_def.h |3 --
drivers/scsi/qla2xxx/qla_fw.h |7 +
drivers/scsi/qla2xxx/qla_gbl.h |4 ++-
drivers/scsi/qla2xxx/qla_init.c |5 +--
driv
From: Seokmann Ju <[EMAIL PROTECTED]>
There is a case where 54xx HBA loads MID firmware as it use 24xx
firmware. In this case, the driver should issue
MBC_MID_INITIALIZE FIRMWARE even though the HBA doesn't support
NPIV. This patch make changes in the driver so that could behave
accordingly.
Sig
From: Adrian Bunk <[EMAIL PROTECTED]>
- make the following needlessly global code static:
- qla_attr.c: qla24xx_vport_delete()
- qla_attr.c: qla24xx_vport_disable()
- qla_mid.c: qla24xx_allocate_vp_id()
- qla_mid.c: qla24xx_find_vhost_by_name()
- qla_mid.c: qla2x00_do_dpc_vp()
- qla_os
From: Seokmann Ju <[EMAIL PROTECTED]>
During vport creation, there was a possibility to get create a
vport with same port_name as pport. A new filter has added to
compare given port_name with the port_name of the pport.
Signed-Off-by: Seokmann Ju <[EMAIL PROTECTED]>
Signed-off-by: Andrew Vasquez
Signed-off-by: Andrew Vasquez <[EMAIL PROTECTED]>
---
drivers/scsi/qla2xxx/qla_isr.c | 12
1 files changed, 12 insertions(+), 0 deletions(-)
diff --git a/drivers/scsi/qla2xxx/qla_isr.c b/drivers/scsi/qla2xxx/qla_isr.c
index 5d2dc92..22216fe 100644
--- a/drivers/scsi/qla2xxx/qla_isr
Subject: [PATCH] scsi-drivers Don't use SG_ALL as allocation size
below list of drivers have used SG_ALL as a size to
preallocate maximum possible command's sg-count.
This is no longer possible since the maximum is not
set at compile time but as a run time configuration.
A better schema
On Thu, 17 Jan 2008, Boaz Harrosh wrote:
> > I don't forsee any issues with maintaining SG_ALL (~0) usage within
> > qla2xxx and qla4xxx, as the number of unused entries on the HBA's
> > request-queue shall ultimately be the rate-limiting factor.
> >
> > --
> Please forgive me I have forgot to pu
Some flash parts have a slow enable write-protection (WP)
operation whereby subsequent FLASH accesses would fail if the WP
operation had not completed. Software now polls the SPI's
status-register for WP completion.
Signed-off-by: Andrew Vasquez <[EMAIL PROTECTED]>
---
drivers/scsi/qla2xxx/qla_s
HBAs supporting these additional counters include ISP24xx and
ISP25xx type boards.
Signed-off-by: Andrew Vasquez <[EMAIL PROTECTED]>
---
drivers/scsi/qla2xxx/qla_attr.c | 44 --
drivers/scsi/qla2xxx/qla_def.h | 22 ++---
drivers/scsi/qla2xxx/qla_gbl.h |7 ++-
drivers
Signed-off-by: Andrew Vasquez <[EMAIL PROTECTED]>
---
drivers/scsi/qla2xxx/qla_isr.c | 85 ++-
1 files changed, 31 insertions(+), 54 deletions(-)
diff --git a/drivers/scsi/qla2xxx/qla_isr.c b/drivers/scsi/qla2xxx/qla_isr.c
index 53cbaff..5d2dc92 100644
--- a/
The driver stores the contents of PCI resources into unsigned
long's before ioremapping. This breaks on 32-bit platforms which
support 64-bit MMIO resources.
Correct code by removing the temporary variables used during MMIO
PIO mapping and using resource_size_t where applicable. Also
correct a sm
The cards being added are supported in a limited sense already through family
matching, but we needed to add some functionality to the driver to expose
selectively the physical drives. These Physical drives are specifically marked
to not be part of any array and thus are declared JBODs (Just a B
As the driver depends on the DPC routine to handle bottom-half
loop resynchronization in order to recover from the issue-lip
request. The issue_lip call is sleeping context capable, so just
issue the reset function there.
Signed-off-by: Andrew Vasquez <[EMAIL PROTECTED]>
---
drivers/scsi/qla2xxx
Original code would clear the buffer after the firmware had
already been initialized to use the buffer, thus potentially
and inadvertantly clearing data previously DMA'd by the
firmware.
Signed-off-by: Andrew Vasquez <[EMAIL PROTECTED]>
---
drivers/scsi/qla2xxx/qla_init.c |2 +-
1 files chang
Signed-off-by: Andrew Vasquez <[EMAIL PROTECTED]>
---
drivers/scsi/qla2xxx/qla_version.h |2 +-
1 files changed, 1 insertions(+), 1 deletions(-)
diff --git a/drivers/scsi/qla2xxx/qla_version.h
b/drivers/scsi/qla2xxx/qla_version.h
index 6e3dc40..2c2f6b4 100644
--- a/drivers/scsi/qla2xxx/qla_v
From: Marcus Barrow <[EMAIL PROTECTED]>
Instead of abusing the semaphore interfaces for mailbox command
completions.
Additional cleanups and
Signed-off-by: Andrew Vasquez <[EMAIL PROTECTED]>
---
drivers/scsi/qla2xxx/qla_def.h |4 +-
drivers/scsi/qla2xxx/qla_gbl.h |2 -
drivers/scsi/qla2x
FCE support enables the firmware to record FC extended link
services and basic link services frames which have been
transmitted and received by the ISP. This allows for a limited
view of the FC traffic through the ISP without using a FC
analyzer. This can be useful in situations where a physical
On Thu, 17 Jan 2008 21:45:39 +0530 Kamalesh Babulal <[EMAIL PROTECTED]> wrote:
> Hi Andrew,
>
> The kernel build fails with following error
>
> drivers/scsi/aha152x.o: In function `aha152x_host_reset_host':
> /home/kamalesh/scrap/linux-2.6.24-rc8/drivers/scsi/aha152x.c:1324: multiple
> definiti
On Thu, 17 Jan 2008, Andrew Vasquez wrote:
> This patchset updates the qla2xxx driver to 8.02.00-k7.
...
BTW: Small typo in the subject, it's obvious these patches aren't for
2.6.24, instead, meant for the next merge window of 2.6.25...
-
To unsubscribe from this list: send the line "unsubscrib
[EMAIL PROTECTED] wrote on Thu, 17 Jan 2008 19:05 +0900:
> On Thu, 17 Jan 2008 12:48:28 +0300
> Vladislav Bolkhovitin <[EMAIL PROTECTED]> wrote:
>
> > FUJITA Tomonori wrote:
> > > On Thu, 17 Jan 2008 10:27:08 +0100
> > > "Bart Van Assche" <[EMAIL PROTECTED]> wrote:
> > >
> > >
> > >>Hello,
> > >
This patchset updates the qla2xxx driver to 8.02.00-k7.
drivers/scsi/qla2xxx/Makefile |2 +-
drivers/scsi/qla2xxx/qla_attr.c| 52 +++--
drivers/scsi/qla2xxx/qla_dbg.c | 37 ++--
drivers/scsi/qla2xxx/qla_dbg.h | 19 ++
drivers/scsi/qla2xxx/qla_def.h | 42 +++--
dri
007 Kai Makisara
+ Copyright 1992 - 2008 Kai Makisara
email [EMAIL PROTECTED]
Some small formal changes - aeb, 950809
@@ -17,7 +17,7 @@
Last modified: 18-JAN-1998 Richard Gooch <[EMAIL PROTECTED]> Devfs support
*/
-static const char *verstr = "20070203";
+static const char *
On Thu, 17 Jan 2008 09:58:11 -0600
James Bottomley <[EMAIL PROTECTED]> wrote:
>
> On Thu, 2008-01-17 at 18:13 +0900, FUJITA Tomonori wrote:
> > On Wed, 16 Jan 2008 14:35:50 +0200
> > Benny Halevy <[EMAIL PROTECTED]> wrote:
> >
> > > On Jan. 15, 2008, 17:20 +0200, James Bottomley <[EMAIL PROTECTE
aha152x.c is built twice - once for the isa driver and once for the
PCMCIA one. Through #ifdefs, the compiled codes are slightly
different; thus, global symbols need to be given different names
depending on which flavor is being built. This patch adds GLOBAL()
macro to aha152x.h which changes the
On Tue, 15 Jan 2008 21:10:50 +0100 (CET)
Stefan Richter <[EMAIL PROTECTED]> wrote:
> Signed-off-by: Stefan Richter <[EMAIL PROTECTED]>
> ---
>
> Replacement of patch "firewire: fw-sbp2: enable s/g chaining".
>
> It's the same, minus '+ .use_sg_chaining = ENABLE_SG_CHAINING,' hunk
> to prevent co
On Fri, Jan 18, 2008 at 09:53:16AM +0900, Tejun Heo wrote:
> aha152x.c is built twice - once for the isa driver and once for the
> PCMCIA one. Through #ifdefs, the compiled codes are slightly
> different; thus, global symbols need to be given different names
> depending on which flavor is being bu
Andrew Morton wrote:
> On Thu, 17 Jan 2008 21:45:39 +0530 Kamalesh Babulal <[EMAIL PROTECTED]> wrote:
>
>> Hi Andrew,
>>
>> The kernel build fails with following error
>>
>> drivers/scsi/aha152x.o: In function `aha152x_host_reset_host':
>> /home/kamalesh/scrap/linux-2.6.24-rc8/drivers/scsi/aha152x
aha152x.c and fdomain are built twice - once for the isa driver and
once for the PCMCIA one. Through #ifdefs, the compiled codes are
slightly different; thus, global symbols need to be given different
names depending on which flavor is being built. This patch adds
GLOBAL() macro to aha152x.h and
On Fri, 18 Jan 2008 12:07:27 +0530 Kamalesh Babulal <[EMAIL PROTECTED]> wrote:
> Hi Andrew,
>
> Patch from Tejun Heo fixes the aha152x.c build failure, and following second
> part
> of the build failure, is still occurring.
>
> drivers/scsi/fdomain.o:(.data+0x0): multiple definition of
> `fdom
On Fri, Jan 18, 2008 at 04:20:40PM +0900, Tejun Heo wrote:
> aha152x.c and fdomain are built twice - once for the isa driver and
> once for the PCMCIA one. Through #ifdefs, the compiled codes are
> slightly different; thus, global symbols need to be given different
> names depending on which flavo
65 matches
Mail list logo