public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Badari Pulavarty <pbadari@us.ibm.com>
To: Daniel McNeil <daniel@osdl.org>
Cc: "linux-aio@kvack.org" <linux-aio@kvack.org>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: [rfc patch 2/2] direct-io: remove address alignment check
Date: Thu, 14 Jul 2005 22:27:59 -0700	[thread overview]
Message-ID: <42D7495F.3030502@us.ibm.com> (raw)
In-Reply-To: <1121384672.6025.81.camel@ibm-c.pdx.osdl.net>

Daniel McNeil wrote:

> On Thu, 2005-07-14 at 16:16, Badari Pulavarty wrote:
> 
>>How does your patch ensures that we meet the driver alignment
>>restrictions ? Like you said, you need atleast "even" byte alignment
>>for IDE etc..
>>
>>And also, are there any restrictions on how much the "minimum" IO
>>size has to be ? I mean, can I read "1" byte ? I guess you are
>>not relaxing it (yet)..
>>
> 
> 
> This patch does not change the i/o size requirements -- they
> must be a multiple of device block size (usually 512).
> 
> It only relaxes the address alignment restriction.  I do not
> know what the driver alignment restrictions are.  Without the
> 1st patch, it was impossible to relax the address space
> check and have direct-io generate the correct i/o's to submit.
> 
> This 2nd patch, is just for testing and generating feedback
> to find out what the address alignment issues are.  Then
> we can decide how to proceed.
> 
> Did you look over the 1st patch?  Comments?

Yes. I did look at the first patch and my questions were basically
towards the first patch. I don't see any enforcement of alignment
with your patch at all. So, we let the driver fail if it can't
handle it ?

BTW, I don't think the first patch is really doing the right thing.
You got little carried away while cleaning up.
You are trying to relax "user buffer" alignment only. If your
"offset" is in the middle of a filesystem block (say 4k), you still
need to zero out the first portion to be able to write into the
middle. That "evil" code is still needed. :(

Thanks,
Badari


  reply	other threads:[~2005-07-15  5:30 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-07-13 23:43 [rfc patch 2/2] direct-io: remove address alignment check Daniel McNeil
2005-07-14 23:16 ` Badari Pulavarty
2005-07-14 23:44   ` Daniel McNeil
2005-07-15  5:27     ` Badari Pulavarty [this message]
2005-07-15 20:06       ` Daniel McNeil
2005-07-15  0:28 ` Tejun Heo
2005-07-15  5:18   ` Badari Pulavarty
2005-07-15  8:23     ` Tejun Heo
2005-07-15 17:54       ` Badari Pulavarty
2005-07-16  3:50         ` Tejun Heo
2005-07-15 16:56     ` Joel Becker
2005-07-15 17:50       ` Badari Pulavarty
2005-07-15 19:16         ` Joel Becker
     [not found] <1121298112.6025.21.camel@ibm-c.pdx.osdl.net.suse.lists.linux.kernel>
2005-07-14 13:18 ` Andi Kleen
2005-07-14 16:02   ` Daniel McNeil
2005-07-14 18:23     ` Andi Kleen
2005-07-14 20:40       ` Daniel McNeil
2005-07-14 23:39         ` Andrew Morton
2005-07-15  0:03           ` Daniel McNeil

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=42D7495F.3030502@us.ibm.com \
    --to=pbadari@us.ibm.com \
    --cc=daniel@osdl.org \
    --cc=linux-aio@kvack.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