linux-fsdevel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Artem Bityutskiy <dedekind1@gmail.com>
To: Christoph Hellwig <hch@lst.de>
Cc: Jens Axboe <axboe@kernel.dk>, linux-fsdevel@vger.kernel.org
Subject: Re: [PATCH, RFC] simplify writeback thread creation
Date: Fri, 09 Jul 2010 18:49:11 +0300	[thread overview]
Message-ID: <1278690551.9953.146.camel@localhost> (raw)
In-Reply-To: <20100709145150.GA5891@lst.de>

On Fri, 2010-07-09 at 16:51 +0200, Christoph Hellwig wrote:
> On Fri, Jul 09, 2010 at 10:52:59AM +0300, Artem Bityutskiy wrote:
> > But what about cases like 'dd if=/dev/zero of=/dev/sda4'? They also
> > involve dirty data write-back.
> 
> But only on the bdev fs inode. 

OK, I do not know details that code and how it works, need to
investigate, but I just thought it is a different case comparing to the
"create bdi task only when an FS is mounter on top". And just wanted to
point that things may be not so elegant.

-- 
Best Regards,
Artem Bityutskiy (Артём Битюцкий)

--
To unsubscribe from this list: send the line "unsubscribe linux-fsdevel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

  reply	other threads:[~2010-07-09 15:53 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-07-07 22:52 [PATCH, RFC] simplify writeback thread creation Christoph Hellwig
2010-07-08  7:08 ` Artem Bityutskiy
2010-07-08 12:20 ` Jens Axboe
2010-07-08 14:21   ` Artem Bityutskiy
2010-07-08 14:59     ` Jens Axboe
2010-07-08 15:23       ` Artem Bityutskiy
2010-07-08 17:23         ` Jens Axboe
2010-07-08 18:43           ` Artem Bityutskiy
2010-07-08 18:48             ` Christoph Hellwig
2010-07-09  7:52               ` Artem Bityutskiy
2010-07-09  8:16                 ` Jens Axboe
2010-07-09 11:06                   ` Theodore Tso
2010-07-09 14:51                 ` Christoph Hellwig
2010-07-09 15:49                   ` Artem Bityutskiy [this message]
2010-07-08 13:22 ` Artem Bityutskiy

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=1278690551.9953.146.camel@localhost \
    --to=dedekind1@gmail.com \
    --cc=axboe@kernel.dk \
    --cc=hch@lst.de \
    --cc=linux-fsdevel@vger.kernel.org \
    /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).