From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1754773Ab1LVDri (ORCPT ); Wed, 21 Dec 2011 22:47:38 -0500 Received: from cantor2.suse.de ([195.135.220.15]:54429 "EHLO mx2.suse.de" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752983Ab1LVDre (ORCPT ); Wed, 21 Dec 2011 22:47:34 -0500 Date: Wed, 21 Dec 2011 19:47:17 -0800 From: Greg KH To: Tim Bird Cc: linux-embedded , linux kernel , Arnd Bergmann , john stultz , Brian Swetland , Kay Sievers , Lennart Poettering Subject: Re: RFC: android logger feedback request Message-ID: <20111222034717.GB14174@suse.de> References: <4EF264C3.6000104@am.sony.com> <20111221231956.GB23859@suse.de> <4EF27B85.9080801@am.sony.com> <20111222005114.GA22541@suse.de> <4EF288B4.1070601@am.sony.com> <20111222014718.GA13085@suse.de> <4EF29217.7040408@am.sony.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <4EF29217.7040408@am.sony.com> User-Agent: Mutt/1.5.21 (2010-09-15) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Wed, Dec 21, 2011 at 06:12:39PM -0800, Tim Bird wrote: > > Again, please see what we are already doing in the kernel and userspace, > > I think a lot of the above is already implemented. > > I don't know what systemd has got going on in user-space. I'm looking > at a very recent kernel, and I see no support for multiple log channels, > or an optimized open/write path. How is the existing syslog read path not "optimized"? What kind of speed and numbers are we talking about here? Oh, and you do know about the userspace printk tty driver, right? What about using that combined with the existing syslog system call? systemd doesn't use it, but I know of a few embedded systems that are already using it today, and I think it might solve the android issues already. thanks, greg k-h