linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: FUJITA Tomonori <fujita.tomonori@lab.ntt.co.jp>
To: hch@lst.de
Cc: vgoyal@redhat.com, jaxboe@fusionio.com, peterz@infradead.org,
	akpm@linux-foundation.org, kay.sievers@vrfy.org,
	viro@zeniv.linux.org.uk, linux-mm@kvack.org,
	linux-fsdevel@vger.kernel.org
Subject: Re: struct backing_dev - purpose and life time rules
Date: Wed, 28 Jul 2010 08:55:43 +0900	[thread overview]
Message-ID: <20100728085458C.fujita.tomonori@lab.ntt.co.jp> (raw)
In-Reply-To: <20100727140947.GA25106@lst.de>

Not a comment on the original topic,

On Tue, 27 Jul 2010 16:09:47 +0200
Christoph Hellwig <hch@lst.de> wrote:

> On Tue, Jul 27, 2010 at 09:39:56AM -0400, Vivek Goyal wrote:
> > How can I do it better?
> > 
> > I needed a unique identifier with which user can work in terms of
> > specifying weights to devices and in terms of understanding what stats
> > mean. Device major/minor number looked like a obivious choice.
> > 
> > I was looking for how to determine what is the major/minor number of disk
> > request queue is associated with and I could use bdi to do that.
> 
> The problem is that a queue can be shared between multiple gendisks,

Is anyone still doing this?

I thought that everyone agreed that this was wrong. Such users (like
MTD) were fixed.

--
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: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>

  reply	other threads:[~2010-07-27 23:56 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-07-27  9:01 Christoph Hellwig
2010-07-27  9:14 ` Christoph Hellwig
2010-07-27 13:39   ` Vivek Goyal
2010-07-27 14:09     ` Christoph Hellwig
2010-07-27 23:55       ` FUJITA Tomonori [this message]
2010-07-28  4:42         ` Kay Sievers

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=20100728085458C.fujita.tomonori@lab.ntt.co.jp \
    --to=fujita.tomonori@lab.ntt.co.jp \
    --cc=akpm@linux-foundation.org \
    --cc=hch@lst.de \
    --cc=jaxboe@fusionio.com \
    --cc=kay.sievers@vrfy.org \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=peterz@infradead.org \
    --cc=vgoyal@redhat.com \
    --cc=viro@zeniv.linux.org.uk \
    /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