From: Chad Talbott <ctalbott@google.com>
To: Gui Jianfeng <guijianfeng@cn.fujitsu.com>
Cc: Vivek Goyal <vgoyal@redhat.com>,
Nauman Rafique <nauman@google.com>,
jens.axboe@oracle.com, linux-kernel@vger.kernel.org,
Li Zefan <lizf@cn.fujitsu.com>
Subject: Re: [PATCH 1/2 V3] io-controller: Add a new interface "weight_device" for IO-Controller
Date: Tue, 9 Mar 2010 21:41:23 -0800 [thread overview]
Message-ID: <1786ab031003092141j48599b09vc80741f35a34d71c@mail.gmail.com> (raw)
In-Reply-To: <4B96E8CC.9080803@cn.fujitsu.com>
On Tue, Mar 9, 2010 at 4:33 PM, Gui Jianfeng <guijianfeng@cn.fujitsu.com> wrote:
> Vivek Goyal wrote:
>> On Tue, Mar 09, 2010 at 09:52:06AM +0800, Gui Jianfeng wrote:
>> I am not very sure but device name/path interface might turn out to be
>> more intutive.
>
> I don't think using an inode path name as interface is a good idea. Because, one
> can create new file to point to the same device. Also, pathname could be removed
> or renamed by user.
> So, i think device number is a better choice.
Sorry to butt in, but I don't think anyone is suggesting trying to
remember names from device nodes. I think the idea is to use the
names derived from the subsystem - such as 'sda' which is reflected in
/sys and dmesg.
Chad
next prev parent reply other threads:[~2010-03-10 5:41 UTC|newest]
Thread overview: 40+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-03-03 6:21 [PATCH 2/1] io-controller: Add a new interface "policy" for IO Controller Gui Jianfeng
2010-03-03 9:01 ` Jens Axboe
2010-03-03 14:33 ` Vivek Goyal
2010-03-03 15:47 ` Vivek Goyal
[not found] ` <e98e18941003031519v14d4f79cg33da5c3cf1f5ac03@mail.gmail.com>
2010-03-04 2:25 ` Chad Talbott
2010-03-04 3:23 ` Gui Jianfeng
2010-03-04 7:35 ` [PATCH 1/2 V2] io-controller: Add a new interface "weight_device" for IO-Controller Gui Jianfeng
2010-03-04 15:24 ` Vivek Goyal
2010-03-05 0:31 ` Gui Jianfeng
2010-03-05 2:25 ` [PATCH 1/2 V3] " Gui Jianfeng
2010-03-05 14:13 ` Vivek Goyal
2010-03-08 19:39 ` Nauman Rafique
2010-03-08 23:09 ` Vivek Goyal
2010-03-09 1:52 ` Gui Jianfeng
2010-03-09 19:03 ` Vivek Goyal
2010-03-10 0:33 ` Gui Jianfeng
2010-03-10 5:41 ` Chad Talbott [this message]
2010-03-10 15:30 ` Vivek Goyal
2010-03-10 17:38 ` Chad Talbott
2010-03-10 18:03 ` Vivek Goyal
2010-03-10 20:31 ` Vivek Goyal
2010-03-11 19:21 ` Manuel Benitez
2010-03-15 13:55 ` Vivek Goyal
2010-03-09 20:16 ` Vivek Goyal
2010-03-09 20:39 ` Nauman Rafique
2010-03-25 6:28 ` Gui Jianfeng
2010-04-07 17:12 ` Chad Talbott
2010-04-07 17:28 ` Vivek Goyal
2010-04-08 0:11 ` Gui Jianfeng
2010-03-05 2:26 ` [PATCH 2/2 V3] io-controller: Document for blkio.weight_device Gui Jianfeng
2010-03-05 2:44 ` Takuya Yoshikawa
2010-03-05 2:42 ` Gui Jianfeng
2010-03-05 14:13 ` Vivek Goyal
2010-03-04 7:35 ` [PATCH 2/2 V2] " Gui Jianfeng
2010-03-04 11:22 ` Takuya Yoshikawa
2010-03-05 0:38 ` Gui Jianfeng
2010-03-04 15:06 ` [PATCH 2/1] io-controller: Add a new interface "policy" for IO Controller Vivek Goyal
2010-03-04 0:27 ` Gui Jianfeng
2010-03-03 15:36 ` Vivek Goyal
2010-03-04 0:29 ` Gui Jianfeng
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1786ab031003092141j48599b09vc80741f35a34d71c@mail.gmail.com \
--to=ctalbott@google.com \
--cc=guijianfeng@cn.fujitsu.com \
--cc=jens.axboe@oracle.com \
--cc=linux-kernel@vger.kernel.org \
--cc=lizf@cn.fujitsu.com \
--cc=nauman@google.com \
--cc=vgoyal@redhat.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).