> It seems overly restrictive to include the whole lock-set, there can
> be multiple non-overlapping putNotify groups within the same lock-set
> since nowadays we do not allow an NPP+NMS link to break a lock-set into
> two.
What are the potential negatives of restricting only one put notify request to be active, while at the same time allowing several put notify requests to be pending initiation, within an entire lock set.
Jeff
______________________________________________________
Jeffrey O. Hill Email [email protected]
LANL MS H820 Voice 505 665 1831
Los Alamos NM 87545 USA FAX 505 665 5107
Message content: TSPA
With sufficient thrust, pigs fly just fine. However, this is
not necessarily a good idea. It is hard to be sure where they
are going to land, and it could be dangerous sitting under them
as they fly overhead. -- RFC 1925
> -----Original Message-----
> From: Andrew Johnson [mailto:[email protected]]
> Sent: Wednesday, November 24, 2010 1:21 PM
> To: Jeff Hill
> Cc: 'Benjamin Franksen'; [email protected]
> Subject: Re: ca_put_callback once again
>
> On Wednesday 24 November 2010 13:52:16 Jeff Hill wrote:
> >
> > Is it possible to know when initiating a put notify if a put notify
> is
> > already pending in any part of the processing chain that it is being
> > initiated, and if so, chain initiation of a subsequent put notify to
> > completion of the pending put notify? My naive understanding is that
> all
> > records in the same processing chain share a single lock set lock,
> and also
> > a single put notify queue?
>
> As currently implemented the putNotify subsystem is fully dynamic, it
> doesn't
> know what records will be processed until they are. I don't see any
> easy way
> to change that since there might be record types such as the seq,
> fanout or
> dfanout where we can't know in advance which links will be processed
> (the SELN
> field value selects one or more links in some modes), and some records
> might
> be disabled using SDIS anyway. It seems overly restrictive to include
> the
> whole lock-set, there can be multiple non-overlapping putNotify groups
> within
> the same lock-set since nowadays we do not allow an NPP+NMS link to
> break a
> lock-set into two.
>
> - Andrew
> --
> If a man is offered a fact which goes against his instincts, he will
> scrutinize it closely, and unless the evidence is overwhelming, he will
> refuse to believe it. If, on the other hand, he is offered something
> which affords a reason for acting in accordance to his instincts, he
> will accept it even on the slightest evidence. -- Bertrand Russell
- Replies:
- Re: ca_put_callback once again Ben Franksen
- References:
- Re: ca_put_callback once again Tim Mooney
- Re: ca_put_callback once again Andrew Johnson
- RE: ca_put_callback once again Jeff Hill
- Re: ca_put_callback once again Andrew Johnson
- Navigate by Date:
- Prev:
Re: ca_put_callback once again Andrew Johnson
- Next:
EPICS Base 3.14.12 released. Andrew Johnson
- Index:
1994
1995
1996
1997
1998
1999
2000
2001
2002
2003
2004
2005
2006
2007
2008
2009
<2010>
2011
2012
2013
2014
2015
2016
2017
2018
2019
2020
2021
2022
2023
2024
- Navigate by Thread:
- Prev:
Re: ca_put_callback once again Andrew Johnson
- Next:
Re: ca_put_callback once again Ben Franksen
- Index:
1994
1995
1996
1997
1998
1999
2000
2001
2002
2003
2004
2005
2006
2007
2008
2009
<2010>
2011
2012
2013
2014
2015
2016
2017
2018
2019
2020
2021
2022
2023
2024
|