From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1755853AbXGURBT (ORCPT ); Sat, 21 Jul 2007 13:01:19 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1751385AbXGURBM (ORCPT ); Sat, 21 Jul 2007 13:01:12 -0400 Received: from ausmtp04.au.ibm.com ([202.81.18.152]:50109 "EHLO ausmtp04.au.ibm.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751278AbXGURBL (ORCPT ); Sat, 21 Jul 2007 13:01:11 -0400 Message-ID: <46A23BC9.2050003@linux.vnet.ibm.com> Date: Sat, 21 Jul 2007 22:30:57 +0530 From: Balbir Singh Reply-To: balbir@linux.vnet.ibm.com Organization: IBM User-Agent: Thunderbird 1.5.0.12 (X11/20070604) MIME-Version: 1.0 To: Paul Menage CC: Andrew Morton , Linux Containers , YAMAMOTO Takashi , Peter Zijlstra , Eric W Biederman , Linux MM Mailing List , Vaidyanathan Srinivasan , Pavel Emelianov , Dave Hansen , Linux Kernel Mailing List Subject: Re: [RFC][-mm PATCH 1/8] Memory controller resource counters (v3) References: <20070720082352.20752.37209.sendpatchset@balbir-laptop> <20070720082403.20752.68425.sendpatchset@balbir-laptop> <6599ad830707201320q25c0ded9v937a365a53d9a77@mail.gmail.com> In-Reply-To: <6599ad830707201320q25c0ded9v937a365a53d9a77@mail.gmail.com> Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Paul Menage wrote: > On 7/20/07, Balbir Singh wrote: >> + >> +ssize_t res_counter_read(struct res_counter *counter, int member, >> + const char __user *userbuf, size_t nbytes, loff_t *pos) >> +{ >> + unsigned long *val; >> + char buf[64], *s; >> + >> + s = buf; >> + val = res_counter_member(counter, member); >> + s += sprintf(s, "%lu\n", *val); >> + return simple_read_from_buffer((void __user *)userbuf, nbytes, >> + pos, buf, s - buf); >> +} > > I think it should be possible to use the support built-in to task > containers to export a uint64 rather than having to create a separate > function here. > That sounds like an easy thing to do, but that means we need to standardize on the uint64 data type for all platforms. >> + >> +ssize_t res_counter_write(struct res_counter *counter, int member, >> + const char __user *userbuf, size_t nbytes, loff_t *pos) >> +{ >> + int ret; >> + char *buf, *end; >> + unsigned long tmp, *val; >> + >> + buf = kmalloc(nbytes + 1, GFP_KERNEL); >> + ret = -ENOMEM; >> + if (buf == NULL) >> + goto out; >> + >> + buf[nbytes] = '\0'; >> + ret = -EFAULT; >> + if (copy_from_user(buf, userbuf, nbytes)) >> + goto out_free; >> + >> + ret = -EINVAL; >> + tmp = simple_strtoul(buf, &end, 10); >> + if (*end != '\0') >> + goto out_free; >> + >> + val = res_counter_member(counter, member); >> + *val = tmp; >> + ret = nbytes; >> +out_free: >> + kfree(buf); >> +out: >> + return ret; >> +} > > I should probably add a generic "write uint64" wraper to task > containers as well. > Sounds good, that will be really helpful. > Paul > > -- > To unsubscribe, send a message with 'unsubscribe linux-mm' in > the body to majordomo@kvack.org. For more info on Linux MM, > see: http://www.linux-mm.org/ . > Don't email: email@kvack.org -- Warm Regards, Balbir Singh Linux Technology Center IBM, ISTL