login
Login
/
Register
Search
Forums
News
Blogs
Features
Site
Home
»
Mailing list archives
»
linux-kernel
»
2007
»
October
»
26
Re: per BDI dirty limit (was Re: -mm merge plans for 2.6.24)
view
thread
!MAILaRCHIVE_VOTE_RePLACE
Previous message: [
thread
] [
date
] [
author
]
Next message: [
thread
] [
date
] [
author
]
[view in full thread]
From:
Peter Zijlstra <peterz@...>
To: Kay Sievers <kay.sievers@...>
Cc: Nick Piggin <nickpiggin@...>, Andrew Morton <akpm@...>, <linux-kernel@...>, Jens Axboe <jens.axboe@...>, Fengguang Wu <fengguang.wu@...>, <greg@...>, Trond Myklebust <trond.myklebust@...>, Miklos Szeredi <miklos@...>
Subject:
Re: per BDI dirty limit (was Re: -mm merge plans for 2.6.24)
Date: Friday, October 26, 2007 - 11:33 am
On Fri, 2007-10-26 at 17:33 +0200, Kay Sievers wrote:
quoted text
> On Fri, 2007-10-26 at 17:22 +0200, Peter Zijlstra wrote: > > On Fri, 2007-10-26 at 17:10 +0200, Kay Sievers wrote: > > > On Fri, 2007-10-26 at 16:48 +0200, Peter Zijlstra wrote: > > > > > > > I appreciate the sysfs people their opinion that /sys/bdi/ might not be the > > > > best from their POV, however I'm not seeing where to hook the BDI object from > > > > so that it all makes sense, a few of the things are currently not exposed in > > > > sysfs at all, like the NFS and FUSE things. > > > > > > What happended to the idea to create a "bdi" class, and have the > > > existing devices as parents, and for stuff that is not (not now, or > > > never) in sysfs, no parent is set. > > > > Must have forgotten about that, mainly because I'm not sure I fully > > understand it. > > > > So we create a class, > > Yes. > > > create these objects, > > Yes, "struct device" objects, assigned to the "bdi" class. (Don't use > class_device, that will be removed soon.) > > > which are all called bdi > > Probably not. You can name it how you want, you can inherit the name of > the parent, or prefix it with whatever fits, they just need to be > unique. Things like the "fuse-%llu" name would work just fine. I guess > you already solved that problem in the debugfs directory. > > > and have children with these attributes in it. > > The attributes would just be files in the device object. > > > Now, I supposed there is a directory that lists all unparented thingies, > > how do I locate the one that matches my nfs mount? > > You look for the name (prefix), try: "ls /sys/class/sound/", it's the > same model all over the place.
Ok, will try that. Is there a 'simple uncluttered' example I could look at to copy from? -
unsubscribe notice
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/
Previous message: [
thread
] [
date
] [
author
]
Next message: [
thread
] [
date
] [
author
]
Messages in current thread:
-mm merge plans for 2.6.24
, Andrew Morton
, (Mon Oct 1, 5:22 pm)
new aops merge [was Re: -mm merge plans for 2.6.24]
, Hugh Dickins
, (Tue Oct 2, 12:21 pm)
kswapd min order, slub max order [was Re: -mm merge plans fo...
, Hugh Dickins
, (Tue Oct 2, 12:06 pm)
Re: kswapd min order, slub max order [was Re: -mm merge plan...
, Nick Piggin
, (Tue Oct 2, 5:10 am)
Re: kswapd min order, slub max order [was Re: -mm merge plan...
, Mel Gorman
, (Tue Oct 2, 2:38 pm)
Re: kswapd min order, slub max order [was Re: -mm merge plan...
, Christoph Lameter
, (Tue Oct 2, 2:28 pm)
Re: kswapd min order, slub max order [was Re: -mm merge plan...
, Christoph Lameter
, (Tue Oct 2, 8:37 pm)
x86 patches was Re: -mm merge plans for 2.6.24
, Andi Kleen
, (Tue Oct 2, 2:18 am)
Re: x86 patches was Re: -mm merge plans for 2.6.24
, Andrew Morton
, (Tue Oct 2, 2:32 am)
Re: x86 patches was Re: -mm merge plans for 2.6.24
, Ingo Molnar
, (Tue Oct 2, 3:37 am)
Re: x86 patches was Re: -mm merge plans for 2.6.24
, Andi Kleen
, (Tue Oct 2, 3:46 am)
Re: x86 patches was Re: -mm merge plans for 2.6.24
, Thomas Gleixner
, (Tue Oct 2, 3:58 am)
Re: x86 patches was Re: -mm merge plans for 2.6.24
, Andi Kleen
, (Tue Oct 2, 3:01 am)
Re: x86 patches was Re: -mm merge plans for 2.6.24
, Andy Whitcroft
, (Tue Oct 2, 5:26 am)
Re: x86 patches was Re: -mm merge plans for 2.6.24
, Andrew Morton
, (Tue Oct 2, 3:18 am)
Re: x86 patches was Re: -mm merge plans for 2.6.24
, KAMEZAWA Hiroyuki
, (Tue Oct 2, 3:36 am)
Re: x86 patches was Re: -mm merge plans for 2.6.24
, Christoph Lameter
, (Tue Oct 2, 2:16 pm)
Re: x86 patches was Re: -mm merge plans for 2.6.24
, Nish Aravamudan
, (Tue Oct 2, 12:40 pm)
Re: x86 patches was Re: -mm merge plans for 2.6.24
, Andrew Morton
, (Tue Oct 2, 3:43 am)
Re: x86 patches was Re: -mm merge plans for 2.6.24
, KAMEZAWA Hiroyuki
, (Tue Oct 2, 4:16 am)
Re: x86 patches was Re: -mm merge plans for 2.6.24
, Christoph Lameter
, (Tue Oct 2, 2:18 pm)
Re: x86 patches was Re: -mm merge plans for 2.6.24
, Yasunori Goto
, (Tue Oct 2, 6:48 am)
Re: x86 patches was Re: -mm merge plans for 2.6.24
, Lee Schermerhorn
, (Tue Oct 2, 1:25 pm)
Re: x86 patches was Re: -mm merge plans for 2.6.24
, Lee Schermerhorn
, (Tue Oct 2, 1:17 pm)
Re: x86 patches was Re: -mm merge plans for 2.6.24
, Matt Mackall
, (Tue Oct 2, 3:55 am)
Re: x86 patches was Re: -mm merge plans for 2.6.24
, Andi Kleen
, (Tue Oct 2, 3:59 am)
Re: -mm merge plans for 2.6.24
, Pekka Enberg
, (Tue Oct 2, 12:12 pm)
A kernel Tracing interface (was Re: -mm merge plans for 2.6....
, David Wilder
, (Wed Oct 3, 3:50 pm)
v4l-stk11xx* [Was: -mm merge plans for 2.6.24]
, Jiri Slaby
, (Tue Oct 2, 3:59 am)
Memory controller merge (was Re: -mm merge plans for 2.6.24)
, Balbir Singh
, (Tue Oct 2, 12:21 am)
Re: Memory controller merge (was Re: -mm merge plans for 2.6...
, Hugh Dickins
, (Tue Oct 2, 11:46 am)
Re: Memory controller merge (was Re: -mm merge plans for 2.6...
, Paul Menage
, (Thu Oct 4, 12:10 pm)
Re: Memory controller merge (was Re: -mm merge plans for 2.6...
, Balbir Singh
, (Wed Oct 3, 4:13 am)
Re: Memory controller merge (was Re: -mm merge plans for 2.6...
, Hugh Dickins
, (Wed Oct 3, 2:47 pm)
Re: Memory controller merge (was Re: -mm merge plans for 2.6...
, Balbir Singh
, (Thu Oct 4, 12:16 am)
Re: Memory controller merge (was Re: -mm merge plans for 2.6...
, Hugh Dickins
, (Thu Oct 4, 9:16 am)
Re: Memory controller merge (was Re: -mm merge plans for 2.6...
, Balbir Singh
, (Thu Oct 4, 11:07 pm)
Re: Memory controller merge (was Re: -mm merge plans for 2.6...
, Hugh Dickins
, (Sun Oct 7, 1:41 pm)
Re: Memory controller merge (was Re: -mm merge plans for 2.6...
, Balbir Singh
, (Sun Oct 7, 10:54 pm)
Re: Memory controller merge (was Re: -mm merge plans for 2.6...
, Rik van Riel
, (Wed Oct 10, 5:07 pm)
Re: Memory controller merge (was Re: -mm merge plans for 2.6...
, Balbir Singh
, (Thu Oct 11, 2:33 am)
writeback fixes
, Fengguang Wu
, (Tue Oct 2, 4:39 am)
Re: -mm merge plans for 2.6.24
, Borislav Petkov
, (Sat Oct 13, 4:44 am)
Re: -mm merge plans for 2.6.24
, Andrew Morton
, (Sat Oct 13, 4:52 am)
Re: -mm merge plans for 2.6.24
, Borislav Petkov
, (Sat Oct 13, 7:45 am)
r/o bind mounts, was Re: -mm merge plans for 2.6.24
, Christoph Hellwig
, (Tue Oct 9, 5:19 am)
remove zero_page (was Re: -mm merge plans for 2.6.24)
, Nick Piggin
, (Tue Oct 2, 1:45 pm)
Re: remove zero_page (was Re: -mm merge plans for 2.6.24)
, Linus Torvalds
, (Wed Oct 3, 11:21 am)
Re: remove zero_page (was Re: -mm merge plans for 2.6.24)
, Nick Piggin
, (Mon Oct 8, 11:17 am)
Re: remove zero_page (was Re: -mm merge plans for 2.6.24)
, Hugh Dickins
, (Tue Oct 9, 9:00 am)
Re: remove zero_page (was Re: -mm merge plans for 2.6.24)
, Linus Torvalds
, (Tue Oct 9, 10:52 am)
Re: remove zero_page (was Re: -mm merge plans for 2.6.24)
, Nick Piggin
, (Tue Oct 9, 5:31 am)
Re: remove zero_page (was Re: -mm merge plans for 2.6.24)
, Linus Torvalds
, (Tue Oct 9, 10:22 pm)
Re: remove zero_page (was Re: -mm merge plans for 2.6.24)
, Nick Piggin
, (Tue Oct 9, 6:15 am)
Re: remove zero_page (was Re: -mm merge plans for 2.6.24)
, Hugh Dickins
, (Wed Oct 10, 12:06 am)
Re: remove zero_page (was Re: -mm merge plans for 2.6.24)
, Linus Torvalds
, (Wed Oct 10, 1:20 am)
Re: remove zero_page (was Re: -mm merge plans for 2.6.24)
, Nick Piggin
, (Tue Oct 9, 10:30 am)
Re: remove zero_page (was Re: -mm merge plans for 2.6.24)
, Linus Torvalds
, (Wed Oct 10, 11:04 am)
Re: remove zero_page (was Re: -mm merge plans for 2.6.24)
, Linus Torvalds
, (Tue Oct 9, 11:06 pm)
Re: remove zero_page (was Re: -mm merge plans for 2.6.24)
, Andrew Morton
, (Wed Oct 3, 6:58 am)
wibbling over the cpuset shed domain connnection
, Paul Jackson
, (Mon Oct 1, 5:34 pm)
Re: wibbling over the cpuset shed domain connnection
, Nick Piggin
, (Tue Oct 2, 8:36 am)
Re: wibbling over the cpuset shed domain connnection
, Paul Jackson
, (Wed Oct 3, 1:21 am)
Re: wibbling over the cpuset shed domain connnection
, Nick Piggin
, (Tue Oct 2, 9:12 am)
Re: wibbling over the cpuset shed domain connnection
, Paul Jackson
, (Wed Oct 3, 3:00 am)
Re: wibbling over the cpuset shed domain connnection
, Andrew Morton
, (Wed Oct 3, 6:57 am)
per BDI dirty limit (was Re: -mm merge plans for 2.6.24)
, Peter Zijlstra
, (Tue Oct 2, 4:17 am)
Re: per BDI dirty limit (was Re: -mm merge plans for 2.6.24)
, Fengguang Wu
, (Tue Oct 2, 4:28 am)
Re: per BDI dirty limit (was Re: -mm merge plans for 2.6.24)
, Martin Knoblauch
, (Wed Oct 3, 7:00 am)
Re: per BDI dirty limit (was Re: -mm merge plans for 2.6.24)
, Andrew Morton
, (Tue Oct 2, 4:31 am)
Re: per BDI dirty limit (was Re: -mm merge plans for 2.6.24)
, Peter Zijlstra
, (Tue Oct 2, 4:48 am)
Re: per BDI dirty limit (was Re: -mm merge plans for 2.6.24)
, Kay Sievers
, (Tue Oct 2, 6:31 am)
Re: per BDI dirty limit (was Re: -mm merge plans for 2.6.24)
, Peter Zijlstra
, (Tue Oct 2, 6:44 am)
Re: per BDI dirty limit (was Re: -mm merge plans for 2.6.24)
, Kay Sievers
, (Tue Oct 2, 7:21 am)
Re: per BDI dirty limit (was Re: -mm merge plans for 2.6.24)
, Peter Zijlstra
, (Tue Oct 2, 7:40 am)
Re: per BDI dirty limit (was Re: -mm merge plans for 2.6.24)
, Kay Sievers
, (Tue Oct 2, 10:38 am)
Re: per BDI dirty limit (was Re: -mm merge plans for 2.6.24)
, Nick Piggin
, (Tue Oct 2, 8:05 am)
Re: per BDI dirty limit (was Re: -mm merge plans for 2.6.24)
, Kay Sievers
, (Wed Oct 3, 6:15 am)
Re: per BDI dirty limit (was Re: -mm merge plans for 2.6.24)
, Peter Zijlstra
, (Wed Oct 3, 6:37 am)
Re: per BDI dirty limit (was Re: -mm merge plans for 2.6.24)
, Kay Sievers
, (Wed Oct 3, 9:35 am)
Re: per BDI dirty limit (was Re: -mm merge plans for 2.6.24)
, Peter Zijlstra
, (Fri Oct 26, 10:48 am)
Re: per BDI dirty limit (was Re: -mm merge plans for 2.6.24)
, Trond Myklebust
, (Fri Oct 26, 12:37 pm)
Re: per BDI dirty limit (was Re: -mm merge plans for 2.6.24)
, Peter Zijlstra
, (Fri Dec 14, 10:50 am)
Re: per BDI dirty limit (was Re: -mm merge plans for 2.6.24)
, Miklos Szeredi
, (Fri Dec 14, 11:14 am)
Re: per BDI dirty limit (was Re: -mm merge plans for 2.6.24)
, Peter Zijlstra
, (Fri Dec 14, 11:54 am)
Re: per BDI dirty limit (was Re: -mm merge plans for 2.6.24)
, Miklos Szeredi
, (Fri Oct 26, 11:06 am)
Re: per BDI dirty limit (was Re: -mm merge plans for 2.6.24)
, Kay Sievers
, (Fri Oct 26, 11:10 am)
Re: per BDI dirty limit (was Re: -mm merge plans for 2.6.24)
, Peter Zijlstra
, (Fri Oct 26, 11:22 am)
Re: per BDI dirty limit (was Re: -mm merge plans for 2.6.24)
, Kay Sievers
, (Fri Oct 26, 11:33 am)
Re: per BDI dirty limit (was Re: -mm merge plans for 2.6.24)
, Peter Zijlstra
, (Fri Oct 26, 11:33 am)
Re: per BDI dirty limit (was Re: -mm merge plans for 2.6.24)
, Kay Sievers
, (Fri Oct 26, 11:55 am)
Re: per BDI dirty limit (was Re: -mm merge plans for 2.6.24)
, Peter Zijlstra
, (Fri Oct 26, 4:04 pm)
Re: per BDI dirty limit (was Re: -mm merge plans for 2.6.24)
, Peter Zijlstra
, (Fri Oct 26, 9:18 pm)
Re: per BDI dirty limit (was Re: -mm merge plans for 2.6.24)
, Greg KH
, (Fri Oct 26, 10:40 pm)
Re: per BDI dirty limit (was Re: -mm merge plans for 2.6.24)
, Peter Zijlstra
, (Sat Oct 27, 4:39 am)
Re: per BDI dirty limit (was Re: -mm merge plans for 2.6.24)
, Greg KH
, (Sat Oct 27, 12:02 pm)
Re: per BDI dirty limit (was Re: -mm merge plans for 2.6.24)
, Kay Sievers
, (Sat Oct 27, 5:08 pm)
Re: per BDI dirty limit (was Re: -mm merge plans for 2.6.24)
, Peter Zijlstra
, (Fri Nov 2, 9:15 am)
Re: per BDI dirty limit (was Re: -mm merge plans for 2.6.24)
, Kay Sievers
, (Fri Nov 2, 9:50 am)
Re: per BDI dirty limit (was Re: -mm merge plans for 2.6.24)
, Peter Zijlstra
, (Fri Nov 2, 10:17 am)
Re: per BDI dirty limit (was Re: -mm merge plans for 2.6.24)
, Kay Sievers
, (Fri Nov 2, 10:32 am)
[PATCH] mm: sysfs: expose the BDI object in sysfs
, Peter Zijlstra
, (Fri Nov 2, 10:59 am)
Re: [PATCH] mm: sysfs: expose the BDI object in sysfs
, Kay Sievers
, (Fri Nov 2, 11:13 am)
Re: per BDI dirty limit (was Re: -mm merge plans for 2.6.24)
, Peter Zijlstra
, (Fri Nov 2, 9:54 am)
Re: per BDI dirty limit (was Re: -mm merge plans for 2.6.24)
, Peter Zijlstra
, (Sat Oct 27, 5:35 pm)
Re: per BDI dirty limit (was Re: -mm merge plans for 2.6.24)
, Greg KH
, (Sun Oct 28, 3:10 am)
Re: per BDI dirty limit (was Re: -mm merge plans for 2.6.24)
, Peter Zijlstra
, (Sat Oct 27, 12:07 pm)
Re: per BDI dirty limit (was Re: -mm merge plans for 2.6.24)
, Peter Zijlstra
, (Wed Oct 3, 9:58 am)
Re: per BDI dirty limit (was Re: -mm merge plans for 2.6.24)
, Fengguang Wu
, (Tue Oct 2, 6:47 am)
Re: per BDI dirty limit (was Re: -mm merge plans for 2.6.24)
, Kay Sievers
, (Tue Oct 2, 7:22 am)
Re: per BDI dirty limit (was Re: -mm merge plans for 2.6.24)
, Fengguang Wu
, (Tue Oct 2, 7:28 am)
Navigation
Create content
Mailing list archives
Recent posts
Popular discussions
linux-kernel
:
jjohansen
[AppArmor 39/45] AppArmor: Profile loading and manipulation, pathname matching
Vladislav Bolkhovitin
Re: Integration of SCST in the mainstream Linux kernel
Heiko Carstens
Re: -mm merge plans for 2.6.23 -- sys_fallocate
Andrew Morton
2.6.23-rc6-mm1
git
:
linux-netdev
:
Gerrit Renker
[PATCH 27/37] dccp: Integration of dynamic feature activation - part 2 (server side)
Evgeniy Polyakov
Re: [BUG] New Kernel Bugs
Jarek Poplawski
[PATCH] pkt_sched: Destroy gen estimators under rtnl_lock().
David Miller
[GIT]: Networking
openbsd-misc
:
Colocation donated by:
Who's online
There are currently
1 user
and
644 guests
online.
Online users
ivy1234
Syndicate