All of lore.kernel.org
 help / color / mirror / Atom feed
From: Borislav Petkov <petkovbb@googlemail.com>
To: bzolnier@gmail.com
Cc: linux-kernel@vger.kernel.org, linux-ide@vger.kernel.org,
	Borislav Petkov <petkovbb@gmail.com>
Subject: [PATCH 0/6] ide-tape: refit tape data buffer bits/kill pipelining-v2
Date: Mon,  7 Apr 2008 06:44:58 +0200	[thread overview]
Message-ID: <1207543504-27888-1-git-send-email-petkovbb@gmail.com> (raw)

Hi Bart,

here's another patchset that contains some other fixes along with the changes
you suggested. We have now a tape->merge_bh buffer which is a singly linked list
of bh's and tape->bh is a pointer within that list. The remaining pipelining
functions have been readjusted to handle the merge buffer. I guess, that was it,
pipelining is gone.

 drivers/ide/ide-tape.c |  215 ++++++++++++++++++++++--------------------------
 1 files changed, 99 insertions(+), 116 deletions(-)

WARNING: multiple messages have this Message-ID (diff)
From: Borislav Petkov <petkovbb@googlemail.com>
To: <bzolnier@gmail.com>
Cc: linux-kernel@vger.kernel.org, linux-ide@vger.kernel.org,
	Borislav Petkov <petkovbb@gmail.com>
Subject: [PATCH 0/6] ide-tape: refit tape data buffer bits/kill pipelining-v2
Date: Mon,  7 Apr 2008 06:44:58 +0200	[thread overview]
Message-ID: <1207543504-27888-1-git-send-email-petkovbb@gmail.com> (raw)

Hi Bart,

here's another patchset that contains some other fixes along with the changes
you suggested. We have now a tape->merge_bh buffer which is a singly linked list
of bh's and tape->bh is a pointer within that list. The remaining pipelining
functions have been readjusted to handle the merge buffer. I guess, that was it,
pipelining is gone.

 drivers/ide/ide-tape.c |  215 ++++++++++++++++++++++--------------------------
 1 files changed, 99 insertions(+), 116 deletions(-)

             reply	other threads:[~2008-04-07  4:44 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-04-07  4:44 Borislav Petkov [this message]
2008-04-07  4:44 ` [PATCH 0/6] ide-tape: refit tape data buffer bits/kill pipelining-v2 Borislav Petkov
2008-04-07  4:44 ` [PATCH 1/6] ide-tape: make __idetape_discard_read_pipeline() of type void Borislav Petkov
2008-04-07  4:44   ` Borislav Petkov
2008-04-07  4:45 ` [PATCH 2/6] ide-tape: mv idetape_discard_read_pipeline ide_tape_discard_merge_buffer Borislav Petkov
2008-04-07  4:45   ` Borislav Petkov
2008-04-07  4:45 ` [PATCH 3/6] ide-tape: mv idetape_empty_write_pipeline ide_tape_flush_merge_buffer Borislav Petkov
2008-04-07  4:45   ` Borislav Petkov
2008-04-07  4:45 ` [PATCH 4/6] ide-tape: mv tape->merge_stage_size tape->merge_bh_size Borislav Petkov
2008-04-07  4:45   ` Borislav Petkov
2008-04-07  4:45 ` [PATCH 5/6] ide-tape: remove tape->merge_stage Borislav Petkov
2008-04-07  4:45   ` Borislav Petkov
2008-04-07  4:45 ` [PATCH 6/6] ide-tape: fix mem leak Borislav Petkov
2008-04-07  4:45   ` Borislav Petkov
2008-04-07 21:11 ` [PATCH 0/6] ide-tape: refit tape data buffer bits/kill pipelining-v2 Bartlomiej Zolnierkiewicz

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=1207543504-27888-1-git-send-email-petkovbb@gmail.com \
    --to=petkovbb@googlemail.com \
    --cc=bzolnier@gmail.com \
    --cc=linux-ide@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=petkovbb@gmail.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.