All of lore.kernel.org
 help / color / mirror / Atom feed
From: Brian Chrisman <brchrisman@gmail.com>
To: Sylar Shen <kimulaaa@gmail.com>
Cc: Sage Weil <sage@newdream.net>, ceph-devel <ceph-devel@vger.kernel.org>
Subject: Re: The cache problem of re-export NFS test
Date: Thu, 14 Apr 2011 05:30:07 -0700	[thread overview]
Message-ID: <BANLkTincrGv4gzxsT0P+5o=h8rLqZGBN+A@mail.gmail.com> (raw)
In-Reply-To: <BANLkTinV8T5Vq8P5grvLtuwxB2BO-T=vLg@mail.gmail.com>

I don't think 'sync' will prevent data from going into cache, it just
means that a copy has to be on stable storage/disk as well.  Whether
there's a copy in memory wont matter.

On Thu, Apr 14, 2011 at 1:52 AM, Sylar Shen <kimulaaa@gmail.com> wrote:
> Hi Sage,
> Thanks for your reply. I really appreciated.
> I tried what you suggested to set the argument "sync" in /etc/exports.
> I also checked "man 5 exports" and it showed that sync means reply to
> requests only after the changes have been committed to stable storage.
> It didn't mention that the export server won't do the cache task.
> However, after I did the experiment, I found that the memory usage of
> Ceph-client still went up to maximum value while writing the data
> which means Ceph-client did the cache task.
> So...are there other possible ways to solve my problem?
> Thanks~~
>
> Best Regards,
> Sylar Shen
>
> 2011/4/12 Sage Weil <sage@newdream.net>:
>> On Tue, 12 Apr 2011, Sylar Shen wrote:
>>> Hi developers,
>>> I know that the following question may not be relative to Ceph but
>>> this confuses me a lot.
>>> I am testing the function of re-exporting nfs by command "dd" without
>>> using buffer.
>>> That means I would like my data to be written to Ceph DFS directly
>>> without passing by the buffer of client or nfs-client.
>>> Here is my test architecture. Hope you could understand what I am
>>> trying to express.....:p
>>> ------------------------------------------------------------------------------
>>>                 nfs                         ceph protocol
>>> Client <------------>Ceph-Client <-------------------> Ceph DFS
>>> ------------------------------------------------------------------------------
>>> I used the command "dd if=/dev/zero of=/mnt/ceph/test bs=64k
>>> count=10000 oflag=dsync"
>>> My purpose was to write the data from the client to Ceph DFS through
>>> Ceph-client.
>>> Ceph DFS was mounted by Ceph-client using Ceph protocol and
>>> Ceph-client was mounted by client using nfs protocol.
>>> I know that my dd command with argument oflag=dsync would write the
>>> data to Ceph-client without using buffer on the client.
>>> But I want my Ceph-client could also just pass the data to Ceph DFS
>>> without using its buffer.
>>> So.....is there any way I can run my scenario?
>>> Or in other words, is there any method I can assure that Ceph-client
>>> won't do the buffer task itself?
>>
>> I think what you're looking for is the 'sync' option in /etc/exports on
>> the ceph-client machine.  See 'man 5 exports'.  That will slow things down
>> considerably but will give you the consistency and safety you're looking
>> for.
>>
>> sage
>>
>
>
>
> --
> Best Regards,
> Sylar Shen
> --
> To unsubscribe from this list: send the line "unsubscribe ceph-devel" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html
>
--
To unsubscribe from this list: send the line "unsubscribe ceph-devel" 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:[~2011-04-14 12:30 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-04-12 14:57 The cache problem of re-export NFS test Sylar Shen
2011-04-12 15:35 ` Sage Weil
2011-04-14  8:52   ` Sylar Shen
2011-04-14 12:30     ` Brian Chrisman [this message]
2011-04-14 12:49       ` Sylar Shen
2011-04-14 15:19         ` Henry Chang
2011-04-14 17:12     ` Sage Weil
2011-04-14 17:56     ` Colin McCabe

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='BANLkTincrGv4gzxsT0P+5o=h8rLqZGBN+A@mail.gmail.com' \
    --to=brchrisman@gmail.com \
    --cc=ceph-devel@vger.kernel.org \
    --cc=kimulaaa@gmail.com \
    --cc=sage@newdream.net \
    /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 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.