All of lore.kernel.org
 help / color / mirror / Atom feed
From: Takahiro Yasui <tyasui@redhat.com>
To: Alasdair G Kergon <agk@redhat.com>
Cc: dm-devel@redhat.com
Subject: Re: [RFC][PATCH 2/4] dm-log: unify rw_header to read/write_header
Date: Mon, 01 Dec 2008 02:24:01 -0500	[thread overview]
Message-ID: <49339111.7000403@redhat.com> (raw)
In-Reply-To: <20081128233747.GC13235@agk.fab.redhat.com>

Alasdair G Kergon wrote:
> On Tue, Nov 25, 2008 at 07:01:39PM -0500, Takahiro Yasui wrote:
>> rw_header function updates three members of io_req data every time
>> when I/O is processed. bi_rw and notify.fn are never modified once
>> they get initialized, and also they can be set in advance.
>> This patch removes unnecessary update operations.
>  
> Indeed.
> 
> And it also removes header_to_disk() from the disk_flush() code
> path but doesn't mention changing that:-)  I assume that's also
> OK because there'll always have been a resume before the flush
> and the data can only change during a resume?

Oh, I'm sorry not to mention it on the patch description, but
your explanation is exactly what I need to do.

>> +++ linux-2.6.28-rc4/drivers/md/dm-log.c
>> @@ -323,20 +323,13 @@ static void header_from_disk(struct log_
> 
>> -static int rw_header(struct log_c *lc, int rw)
> 
> I reckon that little function improves readability/maintainability and I've
> left it in.
> 
> http://www.kernel.org/pub/linux/kernel/people/agk/patches/2.6/editing/
>     dm-log-avoid-reinitialising-io_req-on-every-operation.patch

Thanks, Alasdair. I have removed rw_header function in my patch
since the last two patches don't use it, but your improvement is
fine as a separate patch.

Thanks,
---
Takahiro Yasui
Hitachi Computer Products (America) Inc.

      reply	other threads:[~2008-12-01  7:24 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-11-26  0:01 [RFC][PATCH 2/4] dm-log: unify rw_header to read/write_header Takahiro Yasui
2008-11-28 23:37 ` Alasdair G Kergon
2008-12-01  7:24   ` Takahiro Yasui [this message]

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=49339111.7000403@redhat.com \
    --to=tyasui@redhat.com \
    --cc=agk@redhat.com \
    --cc=dm-devel@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 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.