Bryan Henderson wrote:
You want to *use* the kernel pagecache as much as you can.
No, I really don't. Not always. I can think of only 2 reasons to
maximize my use of the kernel pagecache: 1) saves me duplicating code; 2)
allows me to share resources (memory and disk bandwidth come to mind)
On Wed, 2005-03-02 at 11:30 +0100, Gerhard Schneider wrote:
On Sun, 2005-02-27 at 22:46 +0200, Kai Makisara wrote:
This shows that your application is not using very large block size (3
pages, 10 kB?). You might get better throughput with larger block size (32
kB or 64 kB is usually
On Thu, Feb 17, Alan Stern wrote:
On Thu, 17 Feb 2005, Olaf Hering wrote:
On Mon, Feb 14, Alan Stern wrote:
https://lists.one-eyed-alien.net/pipermail/usb-storage/2004-November/001201.html
Alan,
this patch seems to fix the crashes. Is it ready for production use, or
Thank you, Matt. Then I have another question:
As we know SCSI mid-layer issue a command to LLDD by
host-hostt-queuecommand(cmd, scsi_done); and in the meantime a
timer is set. When the timer expires, SCSI mid-layer know the
execution of command has failed.
My question is: when SCSI
On Wed, 2005-03-02 at 10:49 -0500, Guy wrote:
You did:
dd if=/dev/zero of=/dev/nst0 bs=1M and different mt setblk
Since tape drives can compress data, /dev/zero is a bad source of data,
since it compresses real good. /dev/urandom is a better source.
You would like IBM's LTO-2 tape
u are talking about application aware caching/prefetching stuff. but i
prefer to modifying kernel page cache a little bit while make use of
most of the code there.
That's a powerful argument for using the page cache, and further, for
using it from within the kernel. I once started a project to
except that in iscsi a big chunk of the access patterns are *external*;
eg the real smarts are on that other machine on the network, not in the
iscsi server.
We strayed a little from the topic; I don't claim that a private
user-space cache is better than the page cache for an ISCSI server. My
On Wed, 2005-03-02 at 13:20, Bryan Henderson wrote:
u are talking about application aware caching/prefetching stuff. but i
prefer to modifying kernel page cache a little bit while make use of
most of the code there.
That's a powerful argument for using the page cache, and further, for
A couple patches so that when pending changes to sysfs/hotplug are made,
patches discussed here:
http://marc.theaimsgroup.com/?t=11093974272r=1w=2
We will get the hotplug event for a scsi_device only after all the default
scsi_device attributes are created.
The removal of the
Get rid of the attr_changed_internally(), and always create queue_type and
queue_depth as read/write, and then writes fail if not supported.
Signed-off-by: Patrick Mansfield [EMAIL PROTECTED]
--- linux-2.6.11/drivers/scsi/scsi_sysfs.c 2005-03-02 02:59:50.0
-0800
+++
Use bus dev_attrs to create the default scsi_device attributes.
Note sdev_default_attrs is not a pointer to an array (like
scsi_sysfs_sdev_attrs), and so DEVICE_ATTR's can be removed, and __ATTR
used instaed.
Signed-off-by: Patrick Mansfield [EMAIL PROTECTED]
---
I have an usb-cardreader here that needs some FORCELUN-entries in
scsi_devinfo.c.
lsusb says about the device:
Bus 001 Device 003: ID 0483:1307 SGS Thomson Microelectronics Cytronix 6in1
card reader
Patch see below. Please apply.
--- linux-2.6.11-buju/drivers/scsi/scsi_devinfo.c
On Wed, 2 Mar 2005, Olaf Hering wrote:
When a device is plugged in, rmmod sd_mod fails, does that work for you?
sda is already unregistered, but rmmod is stuck like that:
rmmod D 000F4240 0 11501 4 (NOTLB)
d7a03f1c 0086 db8b95a0 000f4240
13 matches
Mail list logo
