Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1759167Ab2FHH2m (ORCPT ); Fri, 8 Jun 2012 03:28:42 -0400 Received: from smtp.nokia.com ([147.243.128.26]:47567 "EHLO mgw-da02.nokia.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752177Ab2FHH2k convert rfc822-to-8bit (ORCPT ); Fri, 8 Jun 2012 03:28:40 -0400 From: To: CC: , , , , , , , , Subject: RE: [PATCH 2/5] vmevent: Convert from deferred timer to deferred work Thread-Topic: [PATCH 2/5] vmevent: Convert from deferred timer to deferred work Thread-Index: AQHNP/HM8KMmZkc4xkKq2ZDXaeCP2Zbvq0sAgAA7gACAACLOoP//4JWAgAAi/oD//+B6AIAAIckQ Date: Fri, 8 Jun 2012 07:28:18 +0000 Message-ID: <84FF21A720B0874AA94B46D76DB98269045F7918@008-AM1MPN1-004.mgdnok.nokia.com> References: <20120601122118.GA6128@lizard> <1338553446-22292-2-git-send-email-anton.vorontsov@linaro.org> <4FD170AA.10705@gmail.com> <20120608065828.GA1515@lizard> <84FF21A720B0874AA94B46D76DB98269045F7890@008-AM1MPN1-004.mgdnok.nokia.com> <84FF21A720B0874AA94B46D76DB98269045F78E1@008-AM1MPN1-004.mgdnok.nokia.com> In-Reply-To: Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: x-originating-ip: [10.162.61.214] Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 8BIT MIME-Version: 1.0 X-OriginalArrivalTime: 08 Jun 2012 07:28:19.0010 (UTC) FILETIME=[46B8F220:01CD4548] X-Nokia-AV: Clean Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 991 Lines: 19 > -----Original Message----- > From: ext KOSAKI Motohiro [mailto:kosaki.motohiro@gmail.com] > Sent: 08 June, 2012 10:23 ... > > If you wakeup only by signal when memory situation changed you can be > not mlocked. > > Mlocking uses memory very inefficient way and usually cannot be applied > for apps which wants to be notified due to resources restrictions. > > That's your choice. If you don't need to care cache dropping, We don't > enforce it. I only pointed out your explanation was technically incorrect. My explanation is correct. That is an overhead you have to pay if start to use API based on polling from user-space and this overhead narrows API applicability. Moving all times/tracking to kernel avoid useless wakeups in user-space. -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/