linux-ide.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Tejun Heo <tj@home-tj.org>
To: Bartlomiej Zolnierkiewicz <bzolnier@gmail.com>
Cc: linux-kernel@vger.kernel.org, linux-ide@vger.kernel.org
Subject: Re: [PATCH 2.6.11-rc2] ide: merge do_rw_taskfile() and flagged_taskfile() into do_taskfile()
Date: Sun, 06 Feb 2005 12:31:21 +0900	[thread overview]
Message-ID: <42058F89.70008@home-tj.org> (raw)
In-Reply-To: <58cb370e050205190469dcb967@mail.gmail.com>

Hello,

Bartlomiej Zolnierkiewicz wrote:
> On Sun, 6 Feb 2005 11:13:31 +0900, Tejun Heo <tj@home-tj.org> wrote:
> 
>> Hello, Bartlomiej.
> 
> 
> Hi,
> 
> 
>> This is a new version of ide_do_taskfile.patch.  Compared to the
>>original do_rw_task(), only one more 'if' is used in the hot path, so
>>I think the performance issue can be ignored now.  Also, there's no
>>userland visible change with this patch.  Everything should work just
>>as it did with do_rw_taskfile()/flagged_taskfile().
>>
>> do_taskfile() is different from do_rw_taskfile() in that
> 
> 
> Is there any gain in changing name to do_taskfile()?
>  

  Well, I was just thinking

  do_rw_taskfile + (do_)flagged_taskfile -> do_taskfile.

  If you like do_rw_taskfile better, I guess that's okay too. :-)

> 
>> - It uses task->data_phase to determine whether it's a DMA command
>>   or not.
> 
> 
> this is user-space visible change
> (it is right thing to do, I just wanted to point the fact)
> 

  Oops, I forgot that.  Still, it was kind of weird before.  If any of 
tf_{in|out}_flags is set, flagged_taskfile() is called and ->data_phase 
was used, but, if none of the flags was set, do_rw_taskfile() was called 
and the command is used to determine the same thing.  But, yeah, it's 
user-visible.

> 
>> do_taskfile() is different from flagged_taskfile() in that
>>
>> - No (TASKFILE_MULTI_IN && !mult_count) check.  ide_taskfile_ioctl()
>>   checks the same thing, so it doesn't change anything.
> 
> 
> The check may be needed.  AFAIR drive->mult_count may change
> before our taskfile request is started.
> 

  Okay, I'll resurrect that test.

> 
>> - No task->tf_out_flags handling.  ide_end_drive_cmd() ignores it
>>   anyway, so, again, it doesn't change anything.
> 
> 
> I guess you mean ->tf_in_flags?
> 

  Yes.

> 
>> So, what do you think?
> 
> 
> This patch looks much better but could you move writing taskfile
> registers to separate helpers (one for non-flagged and one for flagged)?
> 
> Probably splitting non-flagged taskfile load helper off do_rw_taskfile()
> should be done in separate patch.  We can then use this helper in
> ide-disk.c for __ide_do_rw_taskfile() (we can't do direct conversion
> to do_rw_taskfile() yet for various reasons).

  Sure, I'll do it now.

  Thanks.

-- 
tejun


      reply	other threads:[~2005-02-06  3:31 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-02-06  2:13 [PATCH 2.6.11-rc2] ide: merge do_rw_taskfile() and flagged_taskfile() into do_taskfile() Tejun Heo
2005-02-06  3:04 ` Bartlomiej Zolnierkiewicz
2005-02-06  3:31   ` Tejun Heo [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=42058F89.70008@home-tj.org \
    --to=tj@home-tj.org \
    --cc=bzolnier@gmail.com \
    --cc=linux-ide@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    /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).