From: Lei Yang <lya755@ece.northwestern.edu>
To: Denis Vlasenko <vda@port.imtp.ilyichevsk.odessa.ua>
Cc: linux-kernel@vger.kernel.org, kernelnewbies <kernelnewbies@nl.linux.org>
Subject: Re: set blksize of block device
Date: Thu, 28 Oct 2004 16:20:38 -0500 [thread overview]
Message-ID: <418162A6.80808@ece.northwestern.edu> (raw)
In-Reply-To: <200410280911.15756.vda@port.imtp.ilyichevsk.odessa.ua>
Denis Vlasenko wrote:
>On Thursday 28 October 2004 05:25, Lei Yang wrote:
>
>
>>Or in other words, is there generic routines for block devices such that
>>we could:
>>
>>get (set) block size of a block device;
>>read an existing block (e.g. block 4);
>>write an existing block (e.g. block 5);
>>
>>
>
>Can you stick to "reply below quote" style please?
>
>
OK
>
>
>>>If nobody could answer this question, what about another one? Is there
>>>a system call or a kernel interface that would allow me to write a
>>>
>>>
>
>Can you use read, write and seek system calls?
>--
>vda
>
>
>
>
Not really, as I've explained, I want to do all these stuff in kernel
space. More specifically, I want to write a newbie kernel module. In
this module, I'll do something with a raw block device (with no
filesystem). For example, I want to do block I/O operations on ramdisk,
and I want to set the block size of ramdisk to whatever value I want
(power of 2 of course).
Any comments?
Thanks,
Lei
next prev parent reply other threads:[~2004-10-28 21:35 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-10-27 18:19 set blksize of block device Lei Yang
2004-10-27 18:30 ` Lei Yang
2004-10-28 1:44 ` Lei Yang
2004-10-28 2:25 ` Lei Yang
2004-10-28 6:11 ` Denis Vlasenko
2004-10-28 21:20 ` Lei Yang [this message]
2004-10-28 21:50 ` Todd Poynor
2004-10-28 6:09 ` Denis Vlasenko
2004-10-28 16:35 ` Shesha B. Sreenivasamurthy
2004-10-28 21:04 ` Lei Yang
-- strict thread matches above, loose matches on Subject: below --
2004-10-28 3:34 Bijoy Thomas
2004-10-28 3:42 ` Lei Yang
2004-11-01 13:55 ` Jon Masters
2004-10-28 6:07 gopu.bhaskar
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=418162A6.80808@ece.northwestern.edu \
--to=lya755@ece.northwestern.edu \
--cc=kernelnewbies@nl.linux.org \
--cc=linux-kernel@vger.kernel.org \
--cc=vda@port.imtp.ilyichevsk.odessa.ua \
/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.