On Sat, 2005-03-12 at 11:55 -0500, Dave Wysochanski wrote:
> Alex Aizman wrote:
>
> >
> > This is to announce Open-iSCSI project: High-Performance iSCSI
> > Initiator for
> > Linux.
> >
> > MOTIVATION
> > ==
> >
> > Our initial motivations for the project were: (1) implement the right
> >
Alex Aizman wrote:
This is to announce Open-iSCSI project: High-Performance iSCSI
Initiator for
Linux.
MOTIVATION
==
Our initial motivations for the project were: (1) implement the right
user/kernel split, and (2) design iSCSI data path for performance.
Recently
we added (3): get accepte
On Thu, 2005-03-10 at 11:27 +0100, Lars Marowsky-Bree wrote:
> On 2005-03-09T18:36:37, Alex Aizman <[EMAIL PROTECTED]> wrote:
> > >That works well in our current development series, and if you want to
> > >share code, you can either rip it off (Open Source, we love ya ;) or we
> > >can spin off the
On 2005-03-09T18:36:37, Alex Aizman <[EMAIL PROTECTED]> wrote:
> Heartbeat is good for reliability, etc. WRT "getting paged-out" -
> non-deterministic (things depend on time), right?
Right, if we didn't get scheduled often enough for us to send our
heartbeat messages to the other peers, they'll
Lars Marowsky-Bree wrote:
On 2005-03-08T22:25:29, Alex Aizman <[EMAIL PROTECTED]> wrote:
There's (or at least was up until today) an ongoing discussion on our
mailing list at http://groups-beta.google.com/group/open-iscsi. The
short and long of it: the problem can be solved, and it will. Coupl
Bryan Henderson wrote:
Its fundamental to Unix architecture that user programs sit above the
kernel and get services from the kernel, and turning that on its head so
that the kernel depends on a user space program to do something as
fundamental as a pageout can't come to any good.
Agreed.
Eve
On 2005-03-08T22:25:29, Alex Aizman <[EMAIL PROTECTED]> wrote:
> There's (or at least was up until today) an ongoing discussion on our
> mailing list at http://groups-beta.google.com/group/open-iscsi. The
> short and long of it: the problem can be solved, and it will. Couple
> simple things we
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
>The
>short and long of it: the problem can be solved, and it will. Couple
>simple things we already do: mlockall() to keep the daemon un-swapped,
>and also looking into potential dependency created by syslog (there's
>one for 2.4 kernel, not sure if this is an issue for 2.6).
I think it's pro
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 bi
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 client?
> > > >
> > > Hmm.. x86 executable? sour
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 growin
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 Rea
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 net
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,
This is to announce Open-iSCSI project: High-Performance iSCSI Initiator
for Linux.
MOTIVATION
==
Our initial motivations for the project were: (1) implement the right
user/kernel split, and (2) design iSCSI data path for performance. Recently
we added (3): get accepted into the mainline ke
Alex Aizman wrote:
This is to announce Open-iSCSI project: High-Performance iSCSI Initiator for
Linux.
MOTIVATION
==
Our initial motivations for the project were: (1) implement the right
user/kernel split, and (2) design iSCSI data path for performance. Recently
we added (3): get accepted i
18 matches
Mail list logo
