From: "Janos Haar" <janos.haar@netcenter.hu>
To: "FUJITA Tomonori" <fujita.tomonori@lab.ntt.co.jp>
Cc: <linux-kernel@vger.kernel.org>
Subject: Re: scsi emulation - question
Date: Sat, 7 Aug 2010 12:35:14 +0200 [thread overview]
Message-ID: <026c01cb361c$3c895b10$0400a8c0@dcccs> (raw)
In-Reply-To: 20100808174914A.fujita.tomonori@lab.ntt.co.jp
Hi,
Thanks for the tip.
I have not used this before.
But now i have readed the documentation, and for me it looks like scsi-debug
can work only in RAM and can make only volatile drives.
Have i missed someting? :-)
Thanks,
Janos Haar
----- Original Message -----
From: "FUJITA Tomonori" <fujita.tomonori@lab.ntt.co.jp>
To: <janos.haar@netcenter.hu>
Cc: <linux-kernel@vger.kernel.org>
Sent: Sunday, August 08, 2010 10:50 AM
Subject: Re: scsi emulation - question
> On Sat, 7 Aug 2010 01:26:45 +0200
> "Janos Haar" <janos.haar@netcenter.hu> wrote:
>
>> I am looking for a solution wich can emulate SCSI device from a block
>> device
>> like loop.
>> I need the sg device but not for special commands, but for reading and
>> writing only.
>> I have found only one solution until now, but i want to find better and
>> faster.
>> The actually working is ISCSI target and initiator in one pc.
>> But this opens up port, and makes a lot of IP packets even if i use lo
>> for
>> this, wich is only a waste of time and resources.
>
> scsi-debug should work for you.
> --
> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at http://www.tux.org/lkml/
next prev parent reply other threads:[~2010-08-08 10:36 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-08-06 23:26 scsi emulation - question Janos Haar
2010-08-08 8:50 ` FUJITA Tomonori
2010-08-07 10:35 ` Janos Haar [this message]
2010-08-08 10:43 ` FUJITA Tomonori
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='026c01cb361c$3c895b10$0400a8c0@dcccs' \
--to=janos.haar@netcenter.hu \
--cc=fujita.tomonori@lab.ntt.co.jp \
--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 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.