lists.openwall.net | lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC | |
Open Source and information security mailing list archives
| ||
|
Message-Id: <E1IlQlP-0007W9-00@dorka.pomaz.szeredi.hu> Date: Fri, 26 Oct 2007 17:06:19 +0200 From: Miklos Szeredi <miklos@...redi.hu> To: peterz@...radead.org CC: kay.sievers@...y.org, nickpiggin@...oo.com.au, akpm@...ux-foundation.org, linux-kernel@...r.kernel.org, jens.axboe@...cle.com, fengguang.wu@...il.com, greg@...ah.com, trond.myklebust@....uio.no, miklos@...redi.hu Subject: Re: per BDI dirty limit (was Re: -mm merge plans for 2.6.24) > Subject: bdi: debugfs interface > > Expose the BDI stats (and readahead window) in /debug/bdi/ > > I'm still thinking it should go into /sys somewhere, however I just noticed > not all block devices that have a queue have a /queue directory. Noticeably > those that use make_request_fn() as opposed to request_fn(). And then of > course there are the non-block/non-queue BDIs. > > A BDI is basically the object that represents the 'thing' you dirty pages > against. For block devices that is related to the block device (and is > typically embedded in the queue object), for NFS mounts its the remote server > object of the client. For FUSE, yet again something else. > > 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. > > So, for now, I've exposed the thing in debugfs. Please suggest a better > alternative. > > Miklos, Trond: could you suggest a better fmt for the bdi_init_fmt() for your > respective filesystems? For fuse: err = bdi_init_fmt(&fc->bdi, "fuse-%llu", (unsigned long long) fc->id); This would match the connection ID in /sys/fs/fuse/connections/* Miklos - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@...r.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists