From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Authentication-Results: lists.ozlabs.org; spf=none (no SPF record) smtp.mailfrom=linux.intel.com (client-ip=134.134.136.100; helo=mga07.intel.com; envelope-from=james.feist@linux.intel.com; receiver=) Authentication-Results: lists.ozlabs.org; dmarc=none (p=none dis=none) header.from=linux.intel.com Received: from mga07.intel.com (mga07.intel.com [134.134.136.100]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by lists.ozlabs.org (Postfix) with ESMTPS id 49t5RT63zKzDqtR for ; Fri, 26 Jun 2020 02:43:00 +1000 (AEST) IronPort-SDR: UO0OMdF4zuBbgtTKWlB+jBlOnQefhUWbK9rbR6kJVBeFkmNxNFppEUq1vOGVwUcbtcYzAjPWli DmJrPeKuC+zA== X-IronPort-AV: E=McAfee;i="6000,8403,9663"; a="210063936" X-IronPort-AV: E=Sophos;i="5.75,280,1589266800"; d="scan'208";a="210063936" X-Amp-Result: SKIPPED(no attachment in message) X-Amp-File-Uploaded: False Received: from fmsmga002.fm.intel.com ([10.253.24.26]) by orsmga105.jf.intel.com with ESMTP/TLS/ECDHE-RSA-AES256-GCM-SHA384; 25 Jun 2020 09:42:57 -0700 IronPort-SDR: QiysMI878nxDZ58oeZ1KspYKF9PpgQWCM+gyxlYqKiIjrrXVdPH7/VQ20xJEFym/VK+kVpZKem XAsW9OAjDbDQ== X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="5.75,280,1589266800"; d="scan'208";a="312048817" Received: from jfeist-mobl2.amr.corp.intel.com (HELO [10.212.108.224]) ([10.212.108.224]) by fmsmga002.fm.intel.com with ESMTP; 25 Jun 2020 09:42:56 -0700 Subject: Re: Redfish EventService Implementation To: Brad Bishop , Ratan Gupta , Patrick Williams Cc: "Bills, Jason M" , "Puli, Apparao" , openbmc@lists.ozlabs.org References: <019f5263-a7b2-9cb8-4420-cb597bd29afd@gmail.com> <1d2ad757-826d-1993-b88a-e92010b984ed@linux.vnet.ibm.com> <05ec7793-2efa-42da-ef56-94cc1477d2bb@linux.intel.com> <20200616152428.GA4618@heinlein> <7e16df1c-38b0-d488-dbbf-75fe9ac818ab@linux.intel.com> <68f31493-6db6-8e8e-8486-e03c14685abe@linux.vnet.ibm.com> <20200617204516.GE4618@heinlein> <20ab2d6a-00d8-edc6-a18a-c98d93c6cb3c@linux.vnet.ibm.com> <6d97d36c-b78f-44eb-f808-2ae82184925c@linux.intel.com> <039ec920227046806532803f101345703348b003.camel@fuzziesquirrel.com> From: James Feist Message-ID: Date: Thu, 25 Jun 2020 09:42:56 -0700 User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:68.0) Gecko/20100101 Thunderbird/68.9.0 MIME-Version: 1.0 In-Reply-To: <039ec920227046806532803f101345703348b003.camel@fuzziesquirrel.com> Content-Type: text/plain; charset=utf-8; format=flowed Content-Language: en-US Content-Transfer-Encoding: 7bit X-BeenThere: openbmc@lists.ozlabs.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Development list for OpenBMC List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 25 Jun 2020 16:43:02 -0000 On 6/25/2020 6:45 AM, Brad Bishop wrote: > On Wed, 2020-06-24 at 09:24 -0700, James Feist wrote: >>> 3) bmcweb would monitor the DBUS events >> >> Which events specifically? It seems like it would be monitoring lots >> of events in this proposal. > > Just curious what is the concern around monitoring lots of events? > Performance as always, depending on the number of matches needed. Although a POC could prove this not an issue.