Ack
Thanks
-Nagu
> -Original Message-
> From: Hans Feldt [mailto:osafde...@gmail.com]
> Sent: 30 April 2014 10:31
> To: Nagendra Kumar; Praveen Malviya; hans.nordeb...@ericsson.com
> Cc: opensaf-devel@lists.sourceforge.net
> Subject: [PATCH 1 of 7] amfd: add and use SU assignment count me
osaf/services/saf/logsv/lgs/lgs_stream.c | 4
1 files changed, 0 insertions(+), 4 deletions(-)
In case of close(), the first thing Linux does is deallocate the file
descriptor; then it starts flushing pending written data. If this process is
interrupted, it will return EINTR, but the fil
Summary: log: Log should not retry when close() returns EINTR [#147]
Review request for Trac Ticket(s): 147
Peer Reviewer(s): Mathi/Lennart
Pull request to:
Affected branch(es): 4.3.x
Development branch: 4.3.x
Impacted area Impact y/n
-
Summary: clm: avoid any functional processing from impl_set thread #800
Review request for Trac Ticket(s): #800
Peer Reviewer(s): ramesh.bet...@oracle.com; tony hart @btisystems
Pull request to: <>
Affected branch(es): opensaf-4.3.x, 4.4.x, default
Development branch: <>
--
osaf/services/saf/clmsv/clms/clms.h | 1 +
osaf/services/saf/clmsv/clms/clms_amf.c | 2 ++
osaf/services/saf/clmsv/clms/clms_evt.c | 26 +-
osaf/services/saf/clmsv/clms/clms_imm.c | 18 --
4 files changed, 28 insertions(+), 19 deletions(-)
The st
osaf/services/saf/clmsv/clms/clms_amf.c | 19 +++
osaf/services/saf/clmsv/clms/clms_evt.c | 16 ++--
2 files changed, 21 insertions(+), 14 deletions(-)
I think it is best to first setup the mds and mbcsv role first before
doing any functional processing during role
That's fine then. Especially in the loong run we might support individual
component upgrades too (for middleware services) with appropriate version
adjustments.
Also, as per my previous comment, I think the ETF could have the elements that
are defined as "mandatory" in the SMF spec!
Thanks,
Ma
osaf/tools/safimm/immcfg/imm_cfg.c | 44 +++--
1 files changed, 32 insertions(+), 12 deletions(-)
Enable or Disable notififications using immcfg does not work on a system
running 2PBE.
In the 2PBE the IMM internal object opensafImm=opensafImm,safApp=safImmServic
Summary:Imm:Make immcfg aware of safImmService admin owner for
opensafImm=opensafImm,safApp=safImmService [#840]
Review request for Trac Ticket(s): 840
Peer Reviewer(s): AndersBj, Zoran
Affected branch(es):4.4.x, default
Development branch: default
Docs
On Thursday 01 May 2014 02:30 PM, Hans Feldt wrote:
> Let's be clear that MDS a pure internal opensaf service since quite a long
> time. There are no "applications" to consider at all. This means the only
> thing to care about is in-service performance and making sure
> characteristics are imp
Let's be clear that MDS a pure internal opensaf service since quite a long
time. There are no "applications" to consider at all. This means the only thing
to care about is in-service performance and making sure characteristics are
improved, not regressed.
I am not sure we have to maintain some
On Thursday 01 May 2014 01:04 PM, A V Mahesh wrote:
> On 5/1/2014 10:16 AM, SuryaNarayana Garlapati wrote:
>> The archtype is not a legacy one, it was introduced to have the
>> optimization for the message encoding by the applications.
>
> Passing compile flags `mds_arch=1` `mds_arch=2` (mds_a
On 5/1/2014 10:16 AM, SuryaNarayana Garlapati wrote:
> The archtype is not a legacy one, it was introduced to have the
> optimization for the message encoding by the applications.
Passing compile flags `mds_arch=1` `mds_arch=2` (mds_arch, [The
arch-type input to MDS - valid values 1-7]) , is
13 matches
Mail list logo
