linux-kernel - Re: [SUGGESTION]: drop virtual merge accounting in I/O requests

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-Id: <20080714.052859.88212003.davem@davemloft.net>
Date:	Mon, 14 Jul 2008 05:28:59 -0700 (PDT)
From:	David Miller <davem@...emloft.net>
To:	mpatocka@...hat.com
Cc:	andi@...stfloor.org, sparclinux@...r.kernel.org,
	linux-kernel@...r.kernel.org, jens.axboe@...cle.com
Subject: Re: [SUGGESTION]: drop virtual merge accounting in I/O requests

From: Mikulas Patocka <mpatocka@...hat.com>
Date: Mon, 14 Jul 2008 08:16:13 -0400 (EDT)

> As you mentioned ESP driver, it declares .sg_tablesize = SG_ALL, so 
> BIO_VMERGE_BOUNDARY has no effect on the operation of this driver. Any 
> other driver where BIO_VMERGE_BOUNDARY does matter?

When BIO_VMERGE_BOUNDARY is turned on, requests that would not
otherwise fit into the device's limits, can.

It's the only way to know ahead of time that the IOMMU is going
to merge things for us.
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/