Hello,
i wanted to ask if it is possible to put the typedef Sg_request into sg.h?
The reason i'm asking is, i need to pass data through SG_IO from an
application to the driver. At the moment the problem is solved by copying
code of the SG_IO driver into i2o_config (the passthru function). I'm
Markus Lidel wrote:
Hello,
i wanted to ask if it is possible to put the typedef Sg_request into
sg.h?
A surprising question. I would have though Sg_request was
private to the sg driver but ...
It is possible. Seems as though #if __KERNEL__ conditional
blocks are still acceptable in kernel headers
Hello,
Douglas Gilbert wrote:
Markus Lidel wrote:
i wanted to ask if it is possible to put the typedef Sg_request into
sg.h?
A surprising question. I would have though Sg_request was
private to the sg driver but ...
Yep i know it's not the best way, but the only way to get some data from
an
On 03/08/05 02:00, Andrew Vasquez wrote:
There were some background tasks I shelved until the remote-ports
stuff settled down which I thought could use the deferred processing
thread:
* Initiate LIP -- several customers have asked for this ability as
several topological configurations isolate
On Mon, 7 Mar 2005, Kenn Humborg wrote:
On Mon, Mar 07, 2005 at 09:53:22AM -0800, Brad Boyer wrote:
...
Looks to me like the interrupt came in after the driver already
decided to give up for some reason. I had a big problem with that
while I was trying to fix the driver to use DMA
Hello!
We're seeing a null pointer dereference with certain IDE tape drives on
2.6.11 when we use it with ide-scsi (i686 architecture). The problem is
that the scatter-gather pages aren't mapped to kernel virtual address
space in idescsi_output_buffers()/idescsi_input_buffers(), so, if these
source drivers/scsi/megaraid/Kconfig.megaraid
+source drivers/scsi/megaraid/Kconfig.megaraid_sas
why a fully separate file and not add your ONE config option to
Kconfig.megaraid instead ??
Arjan, I didn't want to needlessly couple megaraid and megaraid_sas.
Since they are in the same
Subject: Re: [ANNOUNCE][PATCH 2.6.11 2/3] megaraid_sas:
Announcing new module for LSI Logic's SAS based MegaRAID controllers
On Fri, Mar 04, 2005 at 10:06:00PM -0500, Bagalkote, Sreenivas wrote:
We are announcing a driver for LSI Logic's new SAS based MegaRAID
controllers.
I'd like to start
+static int is_dma64;
the fact that this is a global variable worries me.
Matt also has the same concern. I am pasting my response from my reply
to his comment:
I will make this an instance parameter if the idea to reduce as many
global variables as possible.
On Tue, Mar 08, 2005 at 06:05:11PM -0500, Bagalkote, Sreenivas wrote:
source drivers/scsi/megaraid/Kconfig.megaraid
+source drivers/scsi/megaraid/Kconfig.megaraid_sas
why a fully separate file and not add your ONE config option to
Kconfig.megaraid instead ??
Arjan, I didn't
Begin forwarded message:
Date: Tue, 8 Mar 2005 13:38:07 + (GMT)
From: Holger Kiehl [EMAIL PROTECTED]
To: linux-kernel linux-kernel@vger.kernel.org
Subject: Fusion-MPT much faster as module
Hello
On a four CPU Opteron compiling the Fusion-MPT as module gives much better
performance when
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,
So, is there a reason we aren't just starting the workq thread
upon the first call to queue something to it ?
-- james s
-Original Message-
From: Luben Tuikov [mailto:[EMAIL PROTECTED]
Sent: Tuesday, March 08, 2005 8:12 AM
To: Andrew Vasquez
Cc: Smart, James;
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 connection (2-way 2.4Ghz Opteron, 64KB block
size);
With what
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:
Matt Mackall wrote:
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.
-
On Tue, 2005-03-08 at 22:05 -0800, Matt Mackall wrote:
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
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
On Tue, 2005-03-08 at 22:50 -0800, Matt Mackall wrote:
On Tue, Mar 08, 2005 at 10:25:58PM -0800, Dmitry Yusupov wrote:
On Tue, 2005-03-08 at 22:05 -0800, Matt Mackall wrote:
On Tue, Mar 08, 2005 at 09:51:39PM -0800, Alex Aizman wrote:
Matt Mackall wrote:
How big is the userspace
21 matches
Mail list logo
