diff options
| author | Eric Sandeen <sandeen@redhat.com> | 2012-12-25 13:33:13 -0500 |
|---|---|---|
| committer | Theodore Ts'o <tytso@mit.edu> | 2012-12-25 13:33:13 -0500 |
| commit | a28a9178e8fcd9b94f7333184ce78e816c8cb2af (patch) | |
| tree | cf841622e5d0eaaa717ee6f10dafcfc185a40132 /fs | |
| parent | ad96f7115593e962dd22a0519021eafaba56f5e3 (diff) | |
| download | linux-a28a9178e8fcd9b94f7333184ce78e816c8cb2af.tar.gz linux-a28a9178e8fcd9b94f7333184ce78e816c8cb2af.tar.bz2 linux-a28a9178e8fcd9b94f7333184ce78e816c8cb2af.zip | |
ext4: remove unaligned AIO warning printk
Although I put this in, I now think it was a bad decision. For most
users, there is very little to be done in this case. They get the
message, once per day, with no real context or proposed action. TBH,
it generates support calls when it probably does not need to; the
message sounds more dire than the situation really is.
Just nuke it. Normal investigation via blktrace or whatnot can
reveal poor IO patterns if bad performance is encountered.
Signed-off-by: Eric Sandeen <sandeen@redhat.com>
Signed-off-by: "Theodore Ts'o" <tytso@mit.edu>
Diffstat (limited to 'fs')
| -rw-r--r-- | fs/ext4/file.c | 8 |
1 files changed, 0 insertions, 8 deletions
diff --git a/fs/ext4/file.c b/fs/ext4/file.c index b64a60bf105a..1c0aad7db1ec 100644 --- a/fs/ext4/file.c +++ b/fs/ext4/file.c @@ -108,14 +108,6 @@ ext4_file_dio_write(struct kiocb *iocb, const struct iovec *iov, /* Unaligned direct AIO must be serialized; see comment above */ if (unaligned_aio) { - static unsigned long unaligned_warn_time; - - /* Warn about this once per day */ - if (printk_timed_ratelimit(&unaligned_warn_time, 60*60*24*HZ)) - ext4_msg(inode->i_sb, KERN_WARNING, - "Unaligned AIO/DIO on inode %ld by %s; " - "performance will be poor.", - inode->i_ino, current->comm); mutex_lock(ext4_aio_mutex(inode)); ext4_unwritten_wait(inode); } |