Remove the estimated Infernalis EOL date, and add the actual EOL date.
As discussed on the ceph-devel mailing list, we decided to say that this
infernalis EOL date is the same date that we made the first Jewel
release available.
Signed-off-by: Ken Dreyer <kdreyer@redhat.com>
unittest_bit_alloc: fix type
Merging before make check because it clearly breaks the build and the build part is done
Reviewed-by: Dan Mick <dmick@redhat.com>
Note that for raw_combined we leak some metadata into the data pool.
Also, we do not account for non-raw metadata or anything else in buffer.h,
as that would pollute the ABI and public interface.
Drop the namespace ceph in buffer.cc (which serves no real purpose) as it
confuses the MEMPOOL_DEFINE_* macros (they cannot be used inside a
namespace).
Signed-off-by: Sage Weil <sage@redhat.com>
Per Greg's recommendation, change the name of this function to better
indicate what it does now that we always request a journal flush on
the last cap flush.
Also, add a comment above the function to better explain why we do this.
Signed-off-by: Jeff Layton <jlayton@redhat.com>
Ensure that we ask the MDS to flush the journal on the last cap flush
from sync_fs and umount codepaths.
Signed-off-by: Jeff Layton <jlayton@redhat.com>
The kernel client lags the userland code a bit, and feature support for
addr2 is not quite ready. Still, we want to allow the client to set the
new flags field in a cap request before then so it can get better fsync
performance.
When we go to update the cap fields, grab the features from the peer,
and verify that the appropriate flags are set before we apply updates
to the btime and change_attr.
Also, just have the function return early if dirty is 0, since it's
a no-op in that case, and turn the comment above the function into
an assertion.
Signed-off-by: Jeff Layton <jlayton@redhat.com>
Ensure that the client will request an immediate journal flush from the
MDS when we'll end up waiting on the flush response. This patch should
fix the fsync codepath, but we may need something similar for syncfs.
Signed-off-by: Jeff Layton <jlayton@redhat.com>
In a later patch, we'll want to have the client set the sync flag in
the cap flush, to hint to the MDS that it should process it immediately.
We could add a second bool, but let's instead do what the kernel client
does which is to have a flags field. With that, the existing no_delay
bool becomes CHECK_CAPS_NODELAY.
We'll add other flags in subsequent patches.
Signed-off-by: Jeff Layton <jlayton@redhat.com>
If the client has set the sync flag in a cap update, then it
is indicating that it's waiting on the reply. Ensure that we flush
the journal in that case.
Signed-off-by: Jeff Layton <jlayton@redhat.com>
Duplicated definition of lambas of same function is not good.
Also switching ExtentMap::rm() to use the new disposer to
keep pace with others.
Signed-off-by: xie xingguo <xie.xingguo@zte.com.cn>
