linux-ide.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Robin Holt <holt@sgi.com>
To: "Luck, Tony" <tony.luck@intel.com>
Cc: Bartlomiej Zolnierkiewicz <bzolnier@gmail.com>,
	"petkovbb@gmail.com" <petkovbb@gmail.com>,
	Nishanth Aravamudan <nacc@us.ibm.com>, Robin Holt <holt@sgi.com>,
	"linux-ia64@vger.kernel.org" <linux-ia64@vger.kernel.org>,
	"linux-ide@vger.kernel.org" <linux-ide@vger.kernel.org>,
	FUJITA Tomonori <fujita.tomonori@lab.ntt.co.jp>
Subject: Re: kernel unaligned accesses on IA64 in IDE
Date: Fri, 22 Aug 2008 14:39:43 -0500	[thread overview]
Message-ID: <20080822193943.GF9457@sgi.com> (raw)
In-Reply-To: <57C9024A16AD2D4C97DC78E552063EA309EDE187@orsmsx505.amr.corp.intel.com>

On Fri, Aug 22, 2008 at 11:51:47AM -0700, Luck, Tony wrote:
> > Why not just make rq->cmd always properly aligned in the block layer
> > i.e. by allocating BLK_MAX_CDB + 2 instead of BLK_MAX_CDB for rq->__cmd
> > and then doing ALIGN() when setting rq->cmd in blk_rq_init()?
> 
> There are two places that do
> 
>         if (rq->cmd != rq->__cmd)
>                 kfree(rq->cmd);
> 
> that would need to be adjusted if you did that.  Better to get __cmd
> aligned on a good boundary by changing the declaration to
> 
>         int __cmd[BLK_MAX_CDB / sizeof (int)];

How about long instead of int.  int leaves us with the possibility that
something else will expect 8 byte alignment.

> and adding a cast to blk_rq_init():
> 
>         rq->cmd = (char *)rq->__cmd;

Robin

  reply	other threads:[~2008-08-22 19:39 UTC|newest]

Thread overview: 27+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-08-19 22:56 kernel unaligned accesses on IA64 in IDE Nishanth Aravamudan
2008-08-20  1:39 ` Peter Chubb
2008-08-21 21:28   ` Nishanth Aravamudan
2008-08-20 14:35 ` Robin Holt
2008-08-21 21:31   ` Nishanth Aravamudan
2008-08-21 21:54     ` Robin Holt
2008-08-22  0:39       ` Nishanth Aravamudan
2008-08-22  1:11         ` Robin Holt
2008-08-22 16:45           ` Nishanth Aravamudan
2008-08-22 10:15         ` Bartlomiej Zolnierkiewicz
2008-08-22 10:55           ` Boris Petkov
2008-08-22 16:45             ` Nishanth Aravamudan
2008-08-22 17:29               ` Boris Petkov
2008-08-22 18:36                 ` Bartlomiej Zolnierkiewicz
2008-08-22 18:51                   ` Luck, Tony
2008-08-22 19:39                     ` Robin Holt [this message]
2008-08-22 20:36                       ` Luck, Tony
2008-08-22 20:41                         ` Borislav Petkov
2008-08-22 20:54                         ` Borislav Petkov
2008-08-22 21:38                           ` Nishanth Aravamudan
2008-08-22 21:49                             ` Borislav Petkov
2008-08-22 21:14                         ` Borislav Petkov
2008-08-22 23:02                           ` Nishanth Aravamudan
2008-08-22 23:30                             ` Luck, Tony
2008-08-22 23:33                               ` James Bottomley
2008-08-22 21:15                         ` James Bottomley
2008-08-25 16:31                           ` Nishanth Aravamudan

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=20080822193943.GF9457@sgi.com \
    --to=holt@sgi.com \
    --cc=bzolnier@gmail.com \
    --cc=fujita.tomonori@lab.ntt.co.jp \
    --cc=linux-ia64@vger.kernel.org \
    --cc=linux-ide@vger.kernel.org \
    --cc=nacc@us.ibm.com \
    --cc=petkovbb@gmail.com \
    --cc=tony.luck@intel.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).