dm-devel.redhat.com archive mirror
 help / color / mirror / Atom feed
From: Jim Ramsay <jim_ramsay@dell.com>
To: Mikulas Patocka <mpatocka@redhat.com>
Cc: dm-devel@redhat.com, Jason_Shamberger@dell.com, agk@redhat.com,
	Kevin_OKelley@dell.com
Subject: Re: [PATCH] reworked dm-switch target
Date: Tue, 11 Sep 2012 09:07:02 -0400	[thread overview]
Message-ID: <20120911130702.GA12315@freewill.lab.equallogic.com> (raw)
In-Reply-To: <Pine.LNX.4.64.1209081219070.13731@file.rdu.redhat.com>


On Sat, Sep 08, 2012 at 12:35:22PM -0400, Mikulas Patocka wrote:
> Your changes are ok, it could be included in the kernel.
> 
> Regarding flushes ... could you please explain how write-back caching 
> works in your design?

We are not actually using write-back caching in our design at all, but
assumed that for a general-purpose DM device like dm-switch, some
underlying storage may rely on REQ_FLUSH to ensure proper data
synchronization, so the switch should do the right thing when required.
The code is modeled on dm-stripe.

> Is there some write-back cache in the host adapter?

No, there is not at this time.

> Is there some write-back cache in the individual storage nodes? (i.e. does 
> the node signal end of I/O before it finishes writing data to the disk) 

No, there is not at this time.  The iSCSI-backed SD devices we are
ultimately using do not advertise any write-back cache ('sdparm
--get=WCE' returns 0).

> Another thing - please resend your code with "Signed-off-by". Read the 
> meaning of "Signed-off-by" in Documentation/SubmittingPatches, agree to 
> the terms and append "Signed-off-by: Jim Ramsay <jim_ramsay@dell.com>" to 
> the code. It is a legal requirement, so that you certify that the code is 
> under the open source license and that you have the right to distribute 
> the code.

Will do shortly.  Thanks!

-- 
Jim Ramsay

  reply	other threads:[~2012-09-11 13:07 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-08-15 22:36 [PATCH] reworked dm-switch target Mikulas Patocka
2012-08-16  7:09 ` Alasdair G Kergon
2012-08-17 14:18   ` Jim_Ramsay
2012-08-20 19:20     ` Mikulas Patocka
2012-08-21 16:33       ` Jim Ramsay
2012-08-21 18:14         ` Alasdair G Kergon
2012-08-22  1:02         ` Mikulas Patocka
2012-08-24 18:14           ` Jim Ramsay
2012-08-30  0:51             ` Mikulas Patocka
2012-09-07 19:58               ` Jim Ramsay
2012-09-08 16:35                 ` Mikulas Patocka
2012-09-11 13:07                   ` Jim Ramsay [this message]
2012-09-11 17:13                     ` Mikulas Patocka
2012-09-11 13:14                   ` Jim Ramsay
2012-08-22  1:03         ` Mikulas Patocka
2012-08-22  1:04         ` Mikulas Patocka
2012-08-20 20:48     ` Alasdair G Kergon

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=20120911130702.GA12315@freewill.lab.equallogic.com \
    --to=jim_ramsay@dell.com \
    --cc=Jason_Shamberger@dell.com \
    --cc=Kevin_OKelley@dell.com \
    --cc=agk@redhat.com \
    --cc=dm-devel@redhat.com \
    --cc=mpatocka@redhat.com \
    /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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).