All of lore.kernel.org
 help / color / mirror / Atom feed
* Is there a way to make Cephfs kernel client to send data to Ceph cluster smoothly with buffer io
@ 2020-11-12 15:17 Sage Meng
  2020-11-12 15:59 ` Jeff Layton
  0 siblings, 1 reply; 3+ messages in thread
From: Sage Meng @ 2020-11-12 15:17 UTC (permalink / raw)
  To: ceph-devel

Hi All,

      Cephfs kernel client is influenced by kernel page cache when we
write data to it,  outgoing data will be huge when os starts to flush
page cache. So Is there a way to make Cephfs kernel client to send
data to ceph cluster smoothly when buffer io is used ? Better a way
that only influence Ceph IO not the whole system IO.

^ permalink raw reply	[flat|nested] 3+ messages in thread

* Re: Is there a way to make Cephfs kernel client to send data to Ceph cluster smoothly with buffer io
  2020-11-12 15:17 Is there a way to make Cephfs kernel client to send data to Ceph cluster smoothly with buffer io Sage Meng
@ 2020-11-12 15:59 ` Jeff Layton
  2020-11-13  2:08   ` Sage Meng
  0 siblings, 1 reply; 3+ messages in thread
From: Jeff Layton @ 2020-11-12 15:59 UTC (permalink / raw)
  To: Sage Meng, ceph-devel

On Thu, 2020-11-12 at 23:17 +0800, Sage Meng wrote:
> Hi All,
> 
>       Cephfs kernel client is influenced by kernel page cache when we
> write data to it,  outgoing data will be huge when os starts to flush
> page cache. So Is there a way to make Cephfs kernel client to send
> data to ceph cluster smoothly when buffer io is used ? Better a way
> that only influence Ceph IO not the whole system IO.

Not really.

The ceph client just does what the VM subsys asks it to do. If the VM
says "write out these pages", then it'll do it -- otherwise they'll just
sit there dirty.

Usually you need to tune things like the dirty_ratio and
dirty_background_ratio to smooth this sort of thing out, but those are
system-wide knobs.

Another alternative is to strategically fsync or syncfs from time to
time, but that's sort of outside the scope of the kernel client.
-- 
Jeff Layton <jlayton@kernel.org>


^ permalink raw reply	[flat|nested] 3+ messages in thread

* Re: Is there a way to make Cephfs kernel client to send data to Ceph cluster smoothly with buffer io
  2020-11-12 15:59 ` Jeff Layton
@ 2020-11-13  2:08   ` Sage Meng
  0 siblings, 0 replies; 3+ messages in thread
From: Sage Meng @ 2020-11-13  2:08 UTC (permalink / raw)
  To: Jeff Layton; +Cc: ceph-devel

It would be nice if there was a mount option to have such parameters
adjusted that only influence CephFS Kernel Client.

Jeff Layton <jlayton@kernel.org> 于2020年11月12日周四 下午11:59写道:
>
> On Thu, 2020-11-12 at 23:17 +0800, Sage Meng wrote:
> > Hi All,
> >
> >       Cephfs kernel client is influenced by kernel page cache when we
> > write data to it,  outgoing data will be huge when os starts to flush
> > page cache. So Is there a way to make Cephfs kernel client to send
> > data to ceph cluster smoothly when buffer io is used ? Better a way
> > that only influence Ceph IO not the whole system IO.
>
> Not really.
>
> The ceph client just does what the VM subsys asks it to do. If the VM
> says "write out these pages", then it'll do it -- otherwise they'll just
> sit there dirty.
>
> Usually you need to tune things like the dirty_ratio and
> dirty_background_ratio to smooth this sort of thing out, but those are
> system-wide knobs.
>
> Another alternative is to strategically fsync or syncfs from time to
> time, but that's sort of outside the scope of the kernel client.
> --
> Jeff Layton <jlayton@kernel.org>
>

^ permalink raw reply	[flat|nested] 3+ messages in thread

end of thread, other threads:[~2020-11-13  2:08 UTC | newest]

Thread overview: 3+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2020-11-12 15:17 Is there a way to make Cephfs kernel client to send data to Ceph cluster smoothly with buffer io Sage Meng
2020-11-12 15:59 ` Jeff Layton
2020-11-13  2:08   ` Sage Meng

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.