From: Michael E Brown <michael_e_brown@dell.com>
To: <linux-kernel@vger.kernel.org>
Cc: "Domsch, Matt" <Matt_Domsch@dell.com>
Subject: Re: [RFC][PATCH] block ioctl to read/write last sector
Date: Wed, 7 Feb 2001 09:35:38 -0600 (CST) [thread overview]
Message-ID: <Pine.LNX.4.30.0102070926030.26194-100000@blap.linuxdev.us.dell.com> (raw)
In-Reply-To: <ouplmrimuid.fsf@pigdrop.muc.suse.de>
On 7 Feb 2001, Andi Kleen wrote:
> But what happens when you e.g. run a software blocksize of 4096 and the device
> has >1 inaccessible 512 byte sector at the end?
> I think it would be better to pass in a offset in 512 byte units to a special
> ioctl (and do error checking in the driver for impossible requests)
This is a valid point.
Can you tell me how it would come about that we would have a blocksize !=
1024?
Can you show the proposed interface to the new ioctl?
I was limited in that I could only figure out how to get one userspace
char* into/out of the ioctl. How would you propose to pass in the offset?
I had problems finding documentation on the more complicated IOCTL calls,
and since I am a kernel hacking novice, I went the easiest and most direct
route.
If you tell me the proposed interface and some sample code, I can code,
test and resubmit it. Thank you for the feedback.
Michael Brown
Linux System Group
Dell Computer Corp
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
Please read the FAQ at http://www.tux.org/lkml/
prev parent reply other threads:[~2001-02-07 15:36 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-02-06 21:34 Michael E Brown
2001-02-07 14:34 ` Andi Kleen
2001-02-07 15:35 ` Michael E Brown [this message]
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=Pine.LNX.4.30.0102070926030.26194-100000@blap.linuxdev.us.dell.com \
--to=michael_e_brown@dell.com \
--cc=Matt_Domsch@dell.com \
--cc=linux-kernel@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
all inboxes | Powered by JetHome®