From mboxrd@z Thu Jan 1 00:00:00 1970 From: Nigel Cunningham Subject: Re: swsusp3: system suspend/resume from userspace Date: Fri, 02 Sep 2005 07:13:32 +1000 Message-ID: <1125609211.4785.32.camel@localhost> References: <20050901201714.GA2027@openzaurus.ucw.cz> Reply-To: ncunningham@linuxmail.org Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="===============81513388354347349==" Return-path: In-Reply-To: <20050901201714.GA2027@openzaurus.ucw.cz> List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: linux-pm-bounces@lists.osdl.org Errors-To: linux-pm-bounces@lists.osdl.org To: Pavel Machek Cc: Linux-pm mailing list List-Id: linux-pm@vger.kernel.org --===============81513388354347349== Content-Type: text/plain Content-Transfer-Encoding: 7bit Hi. On Fri, 2005-09-02 at 06:17, Pavel Machek wrote: > Hi! > > > > shrink kernel a bit at the same time. > > > > got numbers (or predicted numbers)? > > 30-50% of swsusp.c deals with swap writing, and with swsusp3, they could > be removed. Of course, removal would take some time before people install userland > "write image" programs. You're also going to have to add code to interface with userspace and pass the data. I wouldn't be surprised if the net effect is a growth in the code. Regards, Nigel -- Evolution. Enumerate the requirements. Consider the interdependencies. Calculate the probabilities. --===============81513388354347349== Content-Type: text/plain; charset="iso-8859-1" MIME-Version: 1.0 Content-Transfer-Encoding: quoted-printable Content-Disposition: inline --===============81513388354347349==--