mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Kay Sievers" <kay.sievers@vrfy.org>
To: "Miklos Szeredi" <miklos@szeredi.hu>
Cc: neilb@suse.de, a.p.zijlstra@chello.nl, fengguang.wu@gmail.com,
	linux-kernel@vger.kernel.org
Subject: Re: [patch 1/3] bdi patches
Date: Fri, 30 Nov 2007 09:36:31 +0100	[thread overview]
Message-ID: <3ae72650711300036o92832e3ofa7ea02f7ed83222@mail.gmail.com> (raw)
In-Reply-To: <E1Iy0tl-0003qA-2U@dorka.pomaz.szeredi.hu>

On Nov 30, 2007 9:06 AM, Miklos Szeredi <miklos@szeredi.hu> wrote:
> > > Provide a place in sysfs for the backing_dev_info object.
> > > This allows us to see and set the various BDI specific variables.
> >
> > You don't say what the place is, and I'm not quite familiar enough
> > with sysfs internals to figure it out my self.  Help?
>
> /sys/class/bdi  (which sometimes links into /sys/devices/virtual/bdi)
>
> > And while I was looking I noticed that bdi_register (and bdi_init_fmt)
> > takes a second argument 'parent', which is always NULL, and which is
> > undocumented as to purpose.
> > If no-one would ever add another call to bdi_register, why have the
> > second arg, and if they might, how would they know what to put there?

It will get the parent after the block devices are converted from raw
kobjects to core devices. The patch is in Greg's tree.

Kay

  reply	other threads:[~2007-11-30  8:36 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-11-29 11:10 Miklos Szeredi
2007-11-29 11:14 ` [patch 2/3] mm: bdi: allow to set a minimum to the bdi dirty limit Miklos Szeredi
2007-11-29 11:16 ` [patch 3/3] mm: bdi: allow to set a maximum " Miklos Szeredi
2007-11-30  0:52 ` [patch 1/3] bdi patches Neil Brown
2007-11-30  8:06   ` Miklos Szeredi
2007-11-30  8:36     ` Kay Sievers [this message]
2007-12-05 10:22   ` Peter Zijlstra

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=3ae72650711300036o92832e3ofa7ea02f7ed83222@mail.gmail.com \
    --to=kay.sievers@vrfy.org \
    --cc=a.p.zijlstra@chello.nl \
    --cc=fengguang.wu@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=miklos@szeredi.hu \
    --cc=neilb@suse.de \
    /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

all inboxes | Powered by JetHome®