All of lore.kernel.org
 help / color / mirror / Atom feed
From: Greg KH <gregkh@suse.de>
To: Matthew Wilcox <matthew@wil.cx>
Cc: Kay Sievers <kay.sievers@vrfy.org>,
	James Bottomley <James.Bottomley@steeleye.com>,
	FUJITA Tomonori <tomof@acm.org>,
	jens.axboe@oracle.com, hch@infradead.org, jeff@garzik.org,
	hare@suse.de, linux-scsi@vger.kernel.org,
	fujita.tomonori@lab.ntt.co.jp
Subject: Re: [PATCH 3/5] add sg segment limitation info to device structure
Date: Tue, 2 Oct 2007 09:44:13 -0700	[thread overview]
Message-ID: <20071002164413.GA12571@suse.de> (raw)
In-Reply-To: <20071002152534.GT12049@parisc-linux.org>

On Tue, Oct 02, 2007 at 09:25:34AM -0600, Matthew Wilcox wrote:
> On Tue, Oct 02, 2007 at 05:23:39PM +0200, Kay Sievers wrote:
> > Just looking at the number of devices, it seems that allocating it
> > dynamically would be the better deal. We allocate the name of every
> > kobject dynamically today, so I guess it's fine to do that with the
> > DMA data too.
> 
> But we don't need to allocate it dynamically.  We can embed it in the
> pci_dev, eisa_dev, zorro_dev, mca_dev and parisc_device.

But then you run into the issue that James pointed out originally.

Anyway, I don't care which, let's see some patches :)

thanks,

greg k-h

  reply	other threads:[~2007-10-02 16:49 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-09-26  8:58 [PATCH 3/5] add sg segment limitation info to device structure FUJITA Tomonori
2007-09-26 16:05 ` Greg KH
2007-09-27  0:37   ` FUJITA Tomonori
2007-10-01 23:36   ` James Bottomley
2007-10-02  1:39     ` Matthew Wilcox
2007-10-02  4:22       ` Greg KH
2007-10-02 14:45         ` James Bottomley
2007-10-02 15:02           ` Kay Sievers
2007-10-02 15:05             ` James Bottomley
2007-10-02 15:10               ` Kay Sievers
2007-10-02 15:14                 ` James Bottomley
2007-10-02 15:23                   ` Kay Sievers
2007-10-02 15:25                     ` Matthew Wilcox
2007-10-02 16:44                       ` Greg KH [this message]
2007-10-03 14:19                         ` FUJITA Tomonori
2007-10-03 17:57                           ` Jeff Garzik
2007-10-03 21:50                           ` Greg KH

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=20071002164413.GA12571@suse.de \
    --to=gregkh@suse.de \
    --cc=James.Bottomley@steeleye.com \
    --cc=fujita.tomonori@lab.ntt.co.jp \
    --cc=hare@suse.de \
    --cc=hch@infradead.org \
    --cc=jeff@garzik.org \
    --cc=jens.axboe@oracle.com \
    --cc=kay.sievers@vrfy.org \
    --cc=linux-scsi@vger.kernel.org \
    --cc=matthew@wil.cx \
    --cc=tomof@acm.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.