public inbox for linux-scsi@vger.kernel.org
 help / color / mirror / Atom feed
From: Dmitry Yusupov <dmitry_yus@yahoo.com>
To: Matt Mackall <mpm@selenic.com>
Cc: Alex Aizman <itn780@yahoo.com>,
	linux-scsi@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [ANNOUNCE 0/6] Open-iSCSI High-Performance Initiator for Linux
Date: Tue, 08 Mar 2005 22:25:58 -0800	[thread overview]
Message-ID: <1110349558.4451.8.camel@mylaptop> (raw)
In-Reply-To: <20050309060544.GW3120@waste.org>

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 kernel we have approx. 3,300 lines.
> > 
> > >>- 450MB/sec Read on a single connection (2-way 2.4Ghz Opteron, 64KB block 
> > >>size);
> > >
> > >With what network hardware and drives, please?
> > >
> > Neterion's 10GbE adapters. RAM disk on the target side.
> 
> Ahh.
> 
> Snipped my question about userspace deadlocks - that was the important
> one. It is in fact why the sfnet one is written as it is - it
> originally had a userspace component and turned out to be easy to
> deadlock under load because of it.

As Scott Ferris pointed out, the main reason for deadlock in sfnet was
blocking behavior of page cache when daemon tried to do filesystem IO,
namely syslog(). That was 2.4.x kernel. We don't know whether it is
fixed in 2.6.x. If someone knows, please let us know. Meanwhile we came
up with work-around design in user-space. "Paged out" problem fixed
already in our subversion repository by utilizing mlockall() syscall.
Also we have IMHO, working solution for OOM during ERL=0 TCP re-connect.

Dmitry


  parent reply	other threads:[~2005-03-09  6:26 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-03-07  7:03 [ANNOUNCE 0/6] Open-iSCSI High-Performance Initiator for Linux Alex Aizman
2005-03-09  5:04 ` Matt Mackall
2005-03-09  5:51   ` Alex Aizman
2005-03-09  6:05     ` Matt Mackall
2005-03-09  6:25       ` Alex Aizman
2005-03-09 19:29         ` Bryan Henderson
2005-03-09 19:41           ` Matt Mackall
2005-03-10  2:09           ` Alex Aizman
2005-03-09 22:21         ` Lars Marowsky-Bree
2005-03-10  2:36           ` Alex Aizman
2005-03-10 10:27             ` Lars Marowsky-Bree
2005-03-11  7:00               ` Dmitry Yusupov
2005-03-09  6:25       ` Dmitry Yusupov [this message]
2005-03-09  6:50         ` Matt Mackall
2005-03-09  7:18           ` Dmitry Yusupov
     [not found] <4229e34e.7e535078.5bc3.0b5eSMTPIN_ADDED@mx.googlegroups.com>
2005-03-06  1:02 ` Mike Christie
2005-03-12 16:55 ` Dave Wysochanski
2005-03-12 17:08   ` Dmitry Yusupov

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=1110349558.4451.8.camel@mylaptop \
    --to=dmitry_yus@yahoo.com \
    --cc=itn780@yahoo.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-scsi@vger.kernel.org \
    --cc=mpm@selenic.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox