From: Joe Perches <joe@perches.com>
To: Lee Duncan <lduncan@suse.com>
Cc: linux-scsi@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] SCSI, st: modify tape driver to allow writing immediate filemarks
Date: Tue, 07 Feb 2012 17:15:23 -0800 [thread overview]
Message-ID: <1328663723.27428.2.camel@joe2Laptop> (raw)
In-Reply-To: <4F31CAC0.3010905@suse.com>
On Tue, 2012-02-07 at 17:07 -0800, Lee Duncan wrote:
> Add an st module option st_nowait_eof which defaults to 0. Setting this
> option to 1 tells the st driver not to wait when writing a filemark, which
> can result in much faster times on streaming tape drives.
trivial comments:
> diff --git a/drivers/scsi/st.c b/drivers/scsi/st.c
[]
> @@ -81,6 +81,7 @@ static int max_sg_segs;
> static int try_direct_io = TRY_DIRECT_IO;
> static int try_rdio = 1;
> static int try_wdio = 1;
> +static int st_nowait_eof = 0;
Could be bool.
> @@ -1106,6 +1109,11 @@ static int check_tape(struct scsi_tape *STp, struct file *filp)
> STp->drv_buffer));
> }
> STp->drv_write_prot = ((STp->buffer)->b_data[2] & 0x80) != 0;
> + if (!STp->drv_buffer && STp->immediate_filemark) {
> + printk(KERN_WARNING "%s: non-buffered tape: "
> + "disabling writing immediate filemarks", name);
Needs terminating "\n" and it's better to coalesce the
format and ignore 80 char lines to make arbitrary greps
a bit easier.
> diff --git a/drivers/scsi/st.h b/drivers/scsi/st.h
[]
> @@ -120,6 +120,7 @@ struct scsi_tape {
> unsigned char c_algo; /* compression algorithm */
> unsigned char pos_unknown; /* after reset position unknown */
> unsigned char sili; /* use SILI when reading in variable b mode */
> + unsigned char immediate_filemark; /* set immediate bit when writing filemark */
could be bool
next prev parent reply other threads:[~2012-02-08 1:15 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-02-08 1:07 [PATCH] SCSI, st: modify tape driver to allow writing immediate filemarks Lee Duncan
2012-02-08 1:15 ` Joe Perches [this message]
2012-02-09 17:22 ` Lee Duncan
2012-02-08 17:19 ` Kai Makisara
2012-02-09 17:43 ` Lee Duncan
2012-02-28 19:38 ` Kai Makisara
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=1328663723.27428.2.camel@joe2Laptop \
--to=joe@perches.com \
--cc=lduncan@suse.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-scsi@vger.kernel.org \
/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