On Tue, Feb 22 2005, Greg Stark wrote:
Jens Axboe [EMAIL PROTECTED] writes:
fsync has been working all along, since the initial barrier support for
ide. only ext3 and reiserfs support it.
Really? That's huge news. Since what kernel version(s) is that?
Since 2.6.9.
What about a
Jens Axboe [EMAIL PROTECTED] writes:
fsync has been working all along, since the initial barrier support for
ide. only ext3 and reiserfs support it.
Really? That's huge news. Since what kernel version(s) is that?
What about a non-journaled fs, or at least a meta-data-only-journaled fs?
On Mon, Feb 21 2005, Greg Stark wrote:
Jens Axboe [EMAIL PROTECTED] writes:
For the longest time, only the old PATA drivers supported barrier writes
with journalled file systems.
What about for fsync(2)? One of the most frequent sources of data loss on the
postgres mailing list has
Jens Axboe wrote:
On Thu, Jan 27 2005, Jeff Garzik wrote:
Doug Maxey wrote:
On Thu, 27 Jan 2005 13:02:48 +0100, Jens Axboe wrote:
Hi,
For the longest time, only the old PATA drivers supported barrier writes
with journalled file systems. This patch adds support for the same type
of cache flushing
On Fri, Jan 28 2005, Jeff Garzik wrote:
Jens Axboe wrote:
On Thu, Jan 27 2005, Jeff Garzik wrote:
Doug Maxey wrote:
On Thu, 27 Jan 2005 13:02:48 +0100, Jens Axboe wrote:
Hi,
For the longest time, only the old PATA drivers supported barrier writes
with journalled file systems. This
On Fri, Jan 28 2005, Jens Axboe wrote:
On Fri, Jan 28 2005, Jeff Garzik wrote:
Jens Axboe wrote:
On Thu, Jan 27 2005, Jeff Garzik wrote:
Doug Maxey wrote:
On Thu, 27 Jan 2005 13:02:48 +0100, Jens Axboe wrote:
Hi,
For the longest time, only the old PATA drivers supported
On Fri, 2005-01-28 at 10:38 +0100, Jens Axboe wrote:
+/*
+ * snoop succesfull completion of mode select commands that update the
+ * write back cache state
+ */
+#define MS_CACHE_PAGE0x08
+static void sd_snoop_cmd(struct scsi_cmnd *cmd)
+{
+ struct scsi_disk *sdpk;
+ char
On Fri, 2005-01-28 at 10:38 +0100, Jens Axboe wrote:
+/*
+ * snoop succesfull completion of mode select commands that update the
+ * write back cache state
+ */
+#define MS_CACHE_PAGE0x08
+static void sd_snoop_cmd(struct scsi_cmnd *cmd)
+{
+ struct scsi_disk *sdpk;
+ char
Hi,
For the longest time, only the old PATA drivers supported barrier writes
with journalled file systems. This patch adds support for the same type
of cache flushing barriers that PATA uses for SCSI, to be utilized with
libata. It prepares to support barriers with 'real' SCSI hardware that
can
On Thu, 27 Jan 2005 13:02:48 +0100, Jens Axboe wrote:
Hi,
For the longest time, only the old PATA drivers supported barrier writes
with journalled file systems. This patch adds support for the same type
of cache flushing barriers that PATA uses for SCSI, to be utilized with
libata.
What, if
Doug Maxey wrote:
On Thu, 27 Jan 2005 13:02:48 +0100, Jens Axboe wrote:
Hi,
For the longest time, only the old PATA drivers supported barrier writes
with journalled file systems. This patch adds support for the same type
of cache flushing barriers that PATA uses for SCSI, to be utilized with
Jens Axboe wrote:
Hi,
A few changes:
- Cleanup up the driver additions even more, blk_complete_barrier_rq()
does all the work now.
- Fixed up the exports
- Comment functions
- Fixed a bug with SCSI and write back caching disabled
- Rename blk_queue_flush() to blk_queue_flushing() to indicate
On Thu, Jan 27 2005, Jeff Garzik wrote:
Doug Maxey wrote:
On Thu, 27 Jan 2005 13:02:48 +0100, Jens Axboe wrote:
Hi,
For the longest time, only the old PATA drivers supported barrier writes
with journalled file systems. This patch adds support for the same type
of cache flushing barriers
On Thu, Jan 27 2005, Doug Maxey wrote:
On Thu, 27 Jan 2005 13:02:48 +0100, Jens Axboe wrote:
Hi,
For the longest time, only the old PATA drivers supported barrier writes
with journalled file systems. This patch adds support for the same type
of cache flushing barriers that PATA uses for
14 matches
Mail list logo
