From: Alex Aizman <itn780@yahoo.com>
To: Lars Marowsky-Bree <lmb@suse.de>
Cc: Matt Mackall <mpm@selenic.com>,
linux-scsi@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [ANNOUNCE 0/6] Open-iSCSI High-Performance Initiator for Linux
Date: Wed, 09 Mar 2005 18:36:37 -0800 [thread overview]
Message-ID: <422FB2B5.3070803@yahoo.com> (raw)
In-Reply-To: <20050309222114.GF4105@marowsky-bree.de>
Lars Marowsky-Bree wrote:
>On 2005-03-08T22:25:29, Alex Aizman <itn780@yahoo.com> 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 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).
>>
>>
>
>BTW, to get around the very same issues, heartbeat does much the same:
>lock itself into memory, reserve a couple of pages more to spare on
>stack & heap, run at soft-realtime priority.
>
>
Heartbeat is good for reliability, etc. WRT "getting paged-out" -
non-deterministic (things depend on time), right?
>syslog(), however, sucks.
>
>
It does.
>We went down the path of using our non-blocking IPC library to have all
>our various components log to ha_logd, which then logs to syslog() or
>writes to disk or wherever.
>
>
Found ha_logd under http://linux-ha.org. The latter is extemely
interesting in the longer term. In the short term, there's quite a bit
of information on this site, need time.
>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 these parts into a sub-package for you to depend on...
>
>
>
If it's not a big deal :-) let's do the "sub-package" option.
>>The sfnet is a learning experience; it is by no means a proof that it
>>cannot be done.
>>
>>
>
>I'd also argue that it MUST be done, because the current way of "Oh,
>it's somehow related to block stuff, must be in kernel" leads down to
>hell. We better figure out good ways around it ;-)
>
>
Yes, it MUST be done.
>
>Sincerely,
> Lars Marowsky-Brée <lmb@suse.de>
>
>
>
Alex
-
To unsubscribe from this list: send the line "unsubscribe linux-scsi" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
WARNING: multiple messages have this Message-ID (diff)
From: Alex Aizman <itn780@yahoo.com>
To: Lars Marowsky-Bree <lmb@suse.de>
Cc: Matt Mackall <mpm@selenic.com>,
linux-scsi@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [ANNOUNCE 0/6] Open-iSCSI High-Performance Initiator for Linux
Date: Wed, 09 Mar 2005 18:36:37 -0800 [thread overview]
Message-ID: <422FB2B5.3070803@yahoo.com> (raw)
In-Reply-To: <20050309222114.GF4105@marowsky-bree.de>
Lars Marowsky-Bree wrote:
>On 2005-03-08T22:25:29, Alex Aizman <itn780@yahoo.com> 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 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).
>>
>>
>
>BTW, to get around the very same issues, heartbeat does much the same:
>lock itself into memory, reserve a couple of pages more to spare on
>stack & heap, run at soft-realtime priority.
>
>
Heartbeat is good for reliability, etc. WRT "getting paged-out" -
non-deterministic (things depend on time), right?
>syslog(), however, sucks.
>
>
It does.
>We went down the path of using our non-blocking IPC library to have all
>our various components log to ha_logd, which then logs to syslog() or
>writes to disk or wherever.
>
>
Found ha_logd under http://linux-ha.org. The latter is extemely
interesting in the longer term. In the short term, there's quite a bit
of information on this site, need time.
>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 these parts into a sub-package for you to depend on...
>
>
>
If it's not a big deal :-) let's do the "sub-package" option.
>>The sfnet is a learning experience; it is by no means a proof that it
>>cannot be done.
>>
>>
>
>I'd also argue that it MUST be done, because the current way of "Oh,
>it's somehow related to block stuff, must be in kernel" leads down to
>hell. We better figure out good ways around it ;-)
>
>
Yes, it MUST be done.
>
>Sincerely,
> Lars Marowsky-Brée <lmb@suse.de>
>
>
>
Alex
next prev parent reply other threads:[~2005-03-10 2:37 UTC|newest]
Thread overview: 22+ 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-09 22:21 ` Lars Marowsky-Bree
2005-03-10 2:36 ` Alex Aizman [this message]
2005-03-10 2:36 ` Alex Aizman
2005-03-10 10:27 ` Lars Marowsky-Bree
2005-03-10 10:27 ` Lars Marowsky-Bree
2005-03-11 7:00 ` Dmitry Yusupov
2005-03-09 6:25 ` Dmitry Yusupov
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-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=422FB2B5.3070803@yahoo.com \
--to=itn780@yahoo.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-scsi@vger.kernel.org \
--cc=lmb@suse.de \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.