linux-kernel - Re: [RESEND][PATCH v2] block: remove plugging at buffered write time

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

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <20120412142634.GA16559@quack.suse.cz>
Date:	Thu, 12 Apr 2012 16:26:34 +0200
From:	Jan Kara <jack@...e.cz>
To:	Fengguang Wu <fengguang.wu@...el.com>
Cc:	Andrew Morton <akpm@...ux-foundation.org>,
	Jeff Moyer <jmoyer@...hat.com>, Jens Axboe <axboe@...nel.dk>,
	linux-fsdevel@...r.kernel.org, LKML <linux-kernel@...r.kernel.org>,
	Dave Chinner <david@...morbit.com>,
	Christoph Hellwig <hch@...radead.org>, Jan Kara <jack@...e.cz>,
	Chris Mason <chris.mason@...cle.com>,
	Shaohua Li <shli@...ionio.com>
Subject: Re: [RESEND][PATCH v2] block: remove plugging at buffered write
 time

  Hi Fengguang,

On Thu 12-04-12 10:20:40, Wu Fengguang wrote:
> > > > > Note that plugging for O_SYNC writes is also removed. The user may pass
> > > > > arbitrary @size arguments, which may be much larger than the preferable
> > > > > I/O size, or may cross extent/device boundaries. Let the lower layers
> > > > > handle the plugging. Otherwise the plugging code here will turn the
> > > > > low level plugging into no-ops.
> > > > 
> > > > I assume you have some numbers to back this up, right?  Care to share
> > > > those?
> > > 
> > > Yes please.
> > > 
> > > We've broken this stuff a few times recently - we should review and
> > > test carefully.
> > 
> > Yes sure. Last time I posted the patch, I did some tests and found no
> > performance changes. Now for 3.3, the tests started days ago have not
> > finished now (partly because it is stalled for quite long time due to
> > unknown reason). The now-available numbers for bs=4k dd's look fine.
> > The pending tests are for bs=1M dd's and some random fio workloads.
> > 
> 
> The changes are basically small enough to be considered noises.
> But anyway here are some interpretations:
> 
> - application visible data write performance (write_bw) is almost the same
> - it slightly reduces the real IOs that hit disk (io_wkB_s, io_rkB_s)
> - disk utilization slightly increased
> - CPU time is slightly reduced
> 
  Well, two of the throughput numbers stand out (in both directions
actually) although they seem to be more extreme configurations so maybe it
is a noise. But maybe it would deserve further check:

> $ ./compare-io bay/*/*-{3.3.0,3.3.0-plug+}
>                    3.3.0               3.3.0-plug+
> ------------------------  ------------------------
...
>                     2.60        +7.1%         2.78  bay/thresh=1M/btrfs-10dd-1-3.3.0
>                     3.72       -12.5%         3.25  bay/thresh=1M/btrfs-1dd-1-3.3.0
...
  I looked at other iostat numbers as well, but seeing quite some changes
in both directions I'd say that those iostat numbers are too noisy to draw
serious conclusion from them.

								Honza

-- 
Jan Kara <jack@...e.cz>
SUSE Labs, CR
--
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/