All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Martin K. Petersen" <martin.petersen@oracle.com>
To: Christoph Hellwig <hch@lst.de>
Cc: Alan Stern <stern@rowland.harvard.edu>,
	Oliver Neukum <oneukum@suse.com>,
	"iommu\@lists.linux-foundation.org" 
	<iommu@lists.linux-foundation.org>,
	Yoshihiro Shimoda <yoshihiro.shimoda.uh@renesas.com>,
	"linux-block\@vger.kernel.org" <linux-block@vger.kernel.org>,
	Linux-Renesas <linux-renesas-soc@vger.kernel.org>,
	"linux-usb\@vger.kernel.org" <linux-usb@vger.kernel.org>
Subject: Re: How to resolve an issue in swiotlb environment?
Date: Thu, 13 Jun 2019 12:57:21 -0400	[thread overview]
Message-ID: <yq14l4ttocu.fsf@oracle.com> (raw)
In-Reply-To: <20190613073900.GC12093@lst.de> (Christoph Hellwig's message of "Thu, 13 Jun 2019 09:39:00 +0200")


Christoph,

> sd.c only supports a few specific sector size, and none of them is
> < 512 bytes:

Yep, while sd.c in theory supported 256-byte logical blocks a while
back, that code was removed since the block layer always operates on
units of 512 bytes.

-- 
Martin K. Petersen	Oracle Linux Engineering

WARNING: multiple messages have this Message-ID (diff)
From: "Martin K. Petersen" <martin.petersen@oracle.com>
To: Christoph Hellwig <hch@lst.de>
Cc: Linux-Renesas <linux-renesas-soc@vger.kernel.org>,
	"linux-usb@vger.kernel.org" <linux-usb@vger.kernel.org>,
	Oliver Neukum <oneukum@suse.com>,
	"linux-block@vger.kernel.org" <linux-block@vger.kernel.org>,
	"iommu@lists.linux-foundation.org"
	<iommu@lists.linux-foundation.org>,
	Alan Stern <stern@rowland.harvard.edu>
Subject: Re: How to resolve an issue in swiotlb environment?
Date: Thu, 13 Jun 2019 12:57:21 -0400	[thread overview]
Message-ID: <yq14l4ttocu.fsf@oracle.com> (raw)
In-Reply-To: <20190613073900.GC12093@lst.de> (Christoph Hellwig's message of "Thu, 13 Jun 2019 09:39:00 +0200")


Christoph,

> sd.c only supports a few specific sector size, and none of them is
> < 512 bytes:

Yep, while sd.c in theory supported 256-byte logical blocks a while
back, that code was removed since the block layer always operates on
units of 512 bytes.

-- 
Martin K. Petersen	Oracle Linux Engineering
_______________________________________________
iommu mailing list
iommu@lists.linux-foundation.org
https://lists.linuxfoundation.org/mailman/listinfo/iommu

  reply	other threads:[~2019-06-13 16:59 UTC|newest]

Thread overview: 52+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-06-03  6:42 How to resolve an issue in swiotlb environment? Yoshihiro Shimoda
2019-06-03  6:42 ` Yoshihiro Shimoda
2019-06-07 12:00 ` Yoshihiro Shimoda
2019-06-07 12:00   ` Yoshihiro Shimoda
2019-06-10  7:31   ` Biju Das
2019-06-10  7:31     ` Biju Das
2019-06-10 11:13   ` Yoshihiro Shimoda
2019-06-10 11:13     ` Yoshihiro Shimoda
2019-06-10 12:32     ` Christoph Hellwig
2019-06-10 12:32       ` Christoph Hellwig
2019-06-10 18:46       ` Alan Stern
2019-06-10 18:46         ` Alan Stern
2019-06-11  6:41         ` Christoph Hellwig
2019-06-11  6:41           ` Christoph Hellwig
2019-06-11 14:51           ` Alan Stern
2019-06-11 14:51             ` Alan Stern
2019-06-12  7:30             ` Christoph Hellwig
2019-06-12  7:30               ` Christoph Hellwig
2019-06-12  8:52               ` Yoshihiro Shimoda
2019-06-12  8:52                 ` Yoshihiro Shimoda
2019-06-12 11:31                 ` Christoph Hellwig
2019-06-12 11:31                   ` Christoph Hellwig
2019-06-13  4:52                   ` Yoshihiro Shimoda
2019-06-13  4:52                     ` Yoshihiro Shimoda
2019-06-12 11:46               ` Oliver Neukum
2019-06-12 11:46                 ` Oliver Neukum
2019-06-12 12:06                 ` Christoph Hellwig
2019-06-12 12:06                   ` Christoph Hellwig
2019-06-12 14:43                   ` Alan Stern
2019-06-12 14:43                     ` Alan Stern
2019-06-13  7:39                     ` Christoph Hellwig
2019-06-13  7:39                       ` Christoph Hellwig
2019-06-13 16:57                       ` Martin K. Petersen [this message]
2019-06-13 16:57                         ` Martin K. Petersen
2019-06-13 17:16                       ` Alan Stern
2019-06-13 17:16                         ` Alan Stern
2019-06-13 18:18                         ` Greg KH
2019-06-13 18:18                           ` Greg KH
2019-06-13 23:01                         ` shuah
2019-06-13 23:01                           ` shuah
2019-06-14 14:44                           ` Alan Stern
2019-06-14 14:44                             ` Alan Stern
2019-06-18 15:28                             ` shuah
2019-06-18 15:28                               ` shuah
2019-06-19 20:23                               ` shuah
2019-06-19 20:23                                 ` shuah
2019-06-19 21:05                                 ` Alan Stern
2019-06-19 21:05                                   ` Alan Stern
2019-06-21 17:43                                   ` Suwan Kim
2019-06-21 17:43                                     ` Suwan Kim
2019-06-11  6:49         ` Yoshihiro Shimoda
2019-06-11  6:49           ` Yoshihiro Shimoda

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=yq14l4ttocu.fsf@oracle.com \
    --to=martin.petersen@oracle.com \
    --cc=hch@lst.de \
    --cc=iommu@lists.linux-foundation.org \
    --cc=linux-block@vger.kernel.org \
    --cc=linux-renesas-soc@vger.kernel.org \
    --cc=linux-usb@vger.kernel.org \
    --cc=oneukum@suse.com \
    --cc=stern@rowland.harvard.edu \
    --cc=yoshihiro.shimoda.uh@renesas.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.