On Mon, 2008-02-04 at 22:43 +, Alan Cox wrote:
better. So for example, I personally suspect that ATA-over-ethernet is way
better than some crazy SCSI-over-TCP crap, but I'm biased for simple and
low-level, and against those crazy SCSI people to begin with.
Current ATAoE isn't. It
On Tue, 2008-01-22 at 22:59 +, Hugh Dickins wrote:
On Tue, 22 Jan 2008, James Bottomley wrote:
libsas looks to be OK because it specifically kmallocs a 512 byte buffer
which should (for off slab data) be 512 byte aligned.
I don't remember the various SLAB and SLOB and SLUB rules
On Mon, Dec 17, 2007 at 11:24:57AM -0800, Randy Dunlap wrote:
On Sun, 16 Dec 2007 21:55:20 + Mel Gorman wrote:
Just using cp to read the file is enough to cause problems but I
included
a very basic program below that produces the BUG_ON checks. Is this a
known
issue or
On Fri, Dec 14, 2007 at 06:02:06PM -0800, Andrew Morton wrote:
On Sat, 15 Dec 2007 01:09:41 + Mel Gorman [EMAIL PROTECTED] wrote:
On (13/12/07 14:29), Andrew Morton didst pronounce:
The simple way seems to be to malloc a large area, touch every page and
then look at the physical
On Fri, Feb 02, 2007 at 11:06:19AM -0500, Mark Lord wrote:
Alan wrote:
If this is the right strategy for disk recovery for a given type of
device then this ought to be an automatic strategy. Most end users will
not have the knowledge to frob about in sysfs, and if the bad sector hits
at the
On Fri, Feb 02, 2007 at 05:58:04PM -0500, Mark Lord wrote:
Matt Mackall wrote:
..
Also worth considering is that spending minutes trying to reread
damaged sectors is likely to accelerate your death spiral. More data
may be recoverable if you give up quickly in a first pass, then go
back
On Mon, Apr 11, 2005 at 05:50:08PM +0200, Fillod Stephane wrote:
Hi Matt and everyone,
I fixed again my previous patch (take2):
* CDROM_PKTCDVD draws dependency
* removing SCSI_IOCTL from displayed options,
as suggested by Milton Miller.
* rewrote ifdefs in the middle of ide.c
On Wed, Mar 09, 2005 at 11:29:03AM -0800, Bryan Henderson wrote:
I'd like to remind everyone that user space processes aside, there's still
a basic ISCSI initiator resource inversion that needs to be fixed to avoid
deadlock:
ISCSI initiator driver sits below the memory pool
(I..e a
On Sun, Mar 06, 2005 at 11:03:14PM -0800, Alex Aizman wrote:
As far as user/kernel, the existing iSCSI initiators bloat the kernel with
ever-growing control plane code, including but not limited to: iSCSI
discovery, Login (Authentication and Operational), session and connection
management,
On Tue, Mar 08, 2005 at 09:51:39PM -0800, Alex Aizman wrote:
Matt Mackall wrote:
How big is the userspace client?
Hmm.. x86 executable? source?
Anyway, there's about 12,000 lines of user space code, and growing. In
the kernel we have approx. 3,300 lines.
- 450MB/sec Read on a single
On Sun, Mar 06, 2005 at 11:04:51PM -0800, Alex Aizman wrote:
SCSI LLDD consists of 3 files:
- iscsi_if.c (iSCSI open interface over netlink);
- iscsi_tcp.[ch] (iSCSI transport over TCP/IP).
Signed-off-by: Alex Aizman [EMAIL PROTECTED]
Signed-off-by:
On Sun, Mar 06, 2005 at 11:12:06PM -0800, Alex Aizman wrote:
+#define iscsi_ptr(_handle) ((void*)(unsigned long)_handle)
+#define iscsi_handle(_ptr) ((uint64_t)(unsigned long)_ptr)
This is a bit wonky. Why is there a distinction?
+#ifndef ISCSI_PROTO_H
+#define ISCSI_PROTO_H
+
+#define
On Sun, Mar 06, 2005 at 11:19:03PM -0800, Alex Aizman wrote:
+The latest development release is available at:
+http://www.open-iscsi.org
I think a URL in Kconfig and the source is sufficient, as this
requires a userspace component which is a better place to bundle the
docs.
--
Mathematics is
13 matches
Mail list logo
