On Tue, Feb 22 2005, Greg Stark wrote:
Jens Axboe [EMAIL PROTECTED] writes:
fsync has been working all along, since the initial barrier support for
ide. only ext3 and reiserfs support it.
Really? That's huge news. Since what kernel version(s) is that?
Since 2.6.9.
What about a
On Tue, 2005-03-01 at 19:22 +0900, FUJITA Tomonori wrote:
From: Arjan van de Ven [EMAIL PROTECTED]
Subject: [Iscsitarget-devel] Re: [ANNOUNCE] iSCSI enterprise target software
Date: Tue, 01 Mar 2005 10:46:03 +0100
fsync or msync() ? I would imagine the target mmaping it's backend in
On Tue, 2005-03-01 at 11:33 +0100, Arjan van de Ven wrote:
On Tue, 2005-03-01 at 19:22 +0900, FUJITA Tomonori wrote:
From: Arjan van de Ven [EMAIL PROTECTED]
Subject: [Iscsitarget-devel] Re: [ANNOUNCE] iSCSI enterprise target software
Date: Tue, 01 Mar 2005 10:46:03 +0100
fsync or
Manu wrote:
Under a fresh Mandrake 10.1 with a 2.6.8 kernel, the Fusion MPT driver
do recognize the HP tape autoloader. The autoloader is composed of tape
drive (on LUN 0) and the changer (on LUN 1).
The message comes from scsi_scan.c :
printk(KERN_WARNING scsi: %s lun%d has a LUN larger
On Tue, Mar 01, 2005 at 05:06:55PM +0800, Zhao, Forrest wrote:
If I surprisingly hot-remove a SCSI disk from HBA manually
without executing echo scsi remove-single-device
h b t l /proc/scsi/scsi, can the hotplug
event be notified to SCSI mid-layer or user space?
I briefly browse
One thing that's implicit in your reasons for wanting to be in the kernel
is that you've chosen to exploit the kernel's page cache. As a user of
the page cache, you have more control from inside the kernel than from
user space. The page cache was designed to be fundamentally invisible to
Hello,
I found that the megaraid driver always fails to reset the
adapter with the following message:
megaraid: resetting the host...
megaraid mbox: reset sequence completed successfully
megaraid: fast sync command timed out
megaraid: reservation reset failed
Ming Zhang wrote:
On Tue, 2005-03-01 at 13:37, Arjan van de Ven wrote:
On Tue, 2005-03-01 at 10:24 -0800, Bryan Henderson wrote:
One thing that's implicit in your reasons for wanting to be in the kernel
is that you've chosen to exploit the kernel's page cache. As a user of
the page cache, you
Please try:
In mbox_post_sync_cmd_fast(...) replace
for (i = 0; i 0xF; i++) {
if (mbox-numstatus != 0xFF) break;
}
with
for (i = 0; i 0xF; i++) {
if (mbox-numstatus != 0xFF) break;
rmb();
}
Additionally, increase the loop counter to a bigger value.
Thanks,
On Tue, 2005-03-01 at 14:01, Vikas Aggarwal wrote:
And If future IET be visioned as an Enterprise Class Array(Multiple
Host-Side Adapters ie., FAs + Multiple Device Side Adapters ie., DAs),
should better be in direct control of all the system-resources without
being pushed out the kernel.
Arjan van de Ven [EMAIL PROTECTED] writes:
You want to *use* the kernel pagecache as much as you can. You do so by
using mmap and such, and msync to force content to disk. That uses the
Last time I checked you couldn't mmap block devices. Has this changed
now? Could be a problem for an iSCSI
Hi,
thanks for the info.
Adding one more 'F' to the loop counter works.
i.e. 0xFF.
Just adding rmb() didn't solve the problem though it
may decrease the necessary counter value.
I don't know this value is ok for environments other than mine.
Bagalkote,
it is hard to beat linux kernel [page] cache performance though.
It's quite easy to beat it for particular applications. You can use
special knowledge about the workload to drop pages that won't be accessed
soon in favor of pages that will, not clean a page that's just going to
get discarded
On Tue, 2005-03-01 at 16:04, Bryan Henderson wrote:
it is hard to beat linux kernel [page] cache performance though.
It's quite easy to beat it for particular applications. You can use
special knowledge about the workload to drop pages that won't be accessed
soon in favor of pages that
On Tue, Mar 01, 2005 at 09:38:34PM +0100, Andi Kleen wrote:
Arjan van de Ven [EMAIL PROTECTED] writes:
You want to *use* the kernel pagecache as much as you can. You do so by
using mmap and such, and msync to force content to disk. That uses the
Last time I checked you couldn't mmap
On Fri, Feb 25, 2005 at 01:26:50PM -0800, Mark Haverkamp wrote:
I wonder if it wouldn't be better to just check the error return before
the index value.
It's all the same to me.
In drivers/scsi/sd.c:sd_probe:
int index;
...
spin_lock(sd_index_lock);
error =
Only indicate irq-handled if that is really true
Driver currently returns IRQ_HANDLED for all interrupts. Fix this.
Signed-off-by: Jeff Garzik [EMAIL PROTECTED]
diff -Nru a/drivers/scsi/3w-9xxx.c b/drivers/scsi/3w-9xxx.c
--- a/drivers/scsi/3w-9xxx.c2005-03-02 02:14:42 -05:00
+++
Remove bogus irq test.
Driver tested irq handler's irq argument against the PCI device's
pci_dev-irq value, a test which would always succeed.
Change this to if (1) to avoid re-indenting the [huge]
interrupt handling code.
Signed-off-by: Jeff Garzik [EMAIL PROTECTED]
diff -Nru
Reduce irq handler indentation level.
The previous patch replaced an always-true test with if (1),
a function change.
This patch simply eliminates the if (1), and reduces the indentation
level of the entire [rather large] interrupt handler code.
No code changes other than eliminating the if (1)
Jeff Garzik wrote:
The previous patch replaced an always-true test with if (1),
a function change.
er, s/function/functional/
-
To unsubscribe from this list: send the line unsubscribe linux-scsi in
the body of a message to [EMAIL PROTECTED]
More majordomo info at
20 matches
Mail list logo
