[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <20080624131858O.fujita.tomonori@lab.ntt.co.jp>
Date: Tue, 24 Jun 2008 13:19:14 +0900
From: FUJITA Tomonori <fujita.tomonori@....ntt.co.jp>
To: david.altobelli@...com
Cc: fujita.tomonori@....ntt.co.jp, linux-kernel@...r.kernel.org,
greg@...ah.com, James.Bottomley@...senPartnership.com,
jens.axboe@...cle.com
Subject: RE: [PATCH][resubmit] HP iLO driver
On Tue, 24 Jun 2008 03:40:33 +0000
"Altobelli, David" <david.altobelli@...com> wrote:
> > -----Original Message-----
> > From: FUJITA Tomonori [mailto:fujita.tomonori@....ntt.co.jp]
> >
> > This driver creates the own device file and user-space applications
> > write a request data to the device file and read the response from it?
>
> Yes, though I would include that the data for the read response is
> supplied by the management processor.
It works with bsg.
bsg is designed to enable user-space applications to send a request to
something in kernel and get the response. For example, bsg is used to
implement the user-space interface to send a request to SAS hardware
and get the response.
> > Would it be better to use the existing infrastructure (block/bsg.c) to
> > do that? With bsg, you don't need to invent your fifo code to enqueue
> > and dequeue requests.
>
> I'm probably missing something, but I need that particular fifo code
> to manage the device queues.
Oops, I overlooked it. OK, even with bsg, the fifo code is necessary.
Probably bsg can make the driver simpler a bit.
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists